Can a change order be signed electronically?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA (adopted by most states), so Change Order Requests may be e-signed. Exceptions include wills, court filings, and other statutorily excluded document types under ESIGN/UETA.

Recommended signer authentication methods

Use at least email verification plus one stronger method (SMS code, SSO, or KBA) for higher-risk changes; add signer identity, intent, and consent evidence to meet the ESIGN four‑part test (intent, consent, attribution, retention). Use 2FA for regulated workflows.

Notarization or witness requirement

Most change orders do not require notarization or witnesses; however, state law may require notary acknowledgement or witness signatures for certain real estate or power-of-attorney related amendments. Check relevant state rules and RON availability; when required, retain notary journal and A/V recording as applicable.

Storage and retention guidance

Store executed change orders as read-only PDFs with retained audit trails. Keep originals for the contract term plus at least three years; follow IRS recordkeeping (IRC §6501(a)) and HIPAA six-year rules (45 CFR §164.530(j)) when applicable. Use encrypted storage and access controls.

Common preparation mistakes

Unclear scope language, missing cost backup, incorrect effective dates, inconsistent party names, and absent approvals are frequent issues; they delay processing, risk non-payment, and can complicate audits and dispute resolution.

HIPAA and eSignature use

Yes for PHI transactions provided the eSignature vendor signs a Business Associate Agreement and technical safeguards are in place. HIPAA requires administrative, physical, and technical protections; retention follows 45 CFR §164.530(j). Confirm vendor HIPAA compliance and execute a BAA before transmitting PHI.

Electronic Signature
Templates
Project Management
Project Management Contract Change Order Request

Project Management Contract Change Order Request

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

Project Management Contract Change Order Request

Project Identification

Project Name Project ID Client Name Service Provider Project Manager (Provider)

Contract Reference Number: Change Order No.: Request Date:

Original Contract Date:

Summary of Proposed Change

Brief Summary Detailed Description of Change Reason for Change

Scope and Deliverables

Affects scope of work: Affects schedule: Requires additional resources: Requires third-party procurement:

Proposed Scope Additions (if any) Out-of-Scope Items (explicit) Deliverables Affected (list up to 3)

Deliverable 1:

Current Acceptance Criteria:

Proposed Acceptance Criteria:

Impact on Deliverable / Schedule:

Deliverable 2:

Current Acceptance Criteria:

Proposed Acceptance Criteria:

Impact on Deliverable / Schedule:

Deliverable 3:

Current Acceptance Criteria:

Proposed Acceptance Criteria:

Impact on Deliverable / Schedule:

Schedule and Milestones

Current Contract Start Date: Proposed Start Date:

Current Contract End Date: Proposed End Date:

Milestones Affected

Budget and Payment

Change in Contract Price (net increase/decrease):

Itemized Cost Breakdown (list up to 3 items)

Item 1 Description

Amount:

Item 2 Description

Amount:

Item 3 Description

Amount:

Proposed Payment Schedule for Change

Administrative and Legal Provisions

Effect of Execution: Upon execution by both parties, this Change Order amends the referenced Contract only to the extent expressly stated herein. All other terms and conditions of the Contract remain in full force and effect.

Commencement of Work: No change work shall commence until this Change Order is fully executed by authorized representatives of both parties. Any work performed prior to execution is at the performing party's risk and may not be compensable unless expressly approved in writing.

Price and Invoicing: Prices stated are exclusive of taxes unless otherwise noted. Provider shall invoice in accordance with the payment schedule above. Invoices for additional work shall include sufficient detail to permit Client verification of charges.

Change Order Validity: Pricing and schedule adjustments proposed in this Change Order shall remain valid for acceptance for a period of 30 calendar days from the Request Date unless otherwise stated in writing.

Liability and Indemnity: Except as expressly modified by this Change Order, the parties' respective liability and indemnity obligations under the Contract continue to apply. This Change Order does not expand or limit any indemnity obligations except as stated herein.

Confidentiality: All non-public information exchanged in connection with this Change Order shall be treated as Confidential Information in accordance with the confidentiality provisions of the Contract.

Governing Law: This Change Order shall be governed by and construed in accordance with the laws governing the Contract. Any dispute arising out of this Change Order shall be resolved in accordance with the Contract's dispute resolution provisions.

Additional Conditions or Notes Attachments

Acknowledgment and Certification

By signing below, the undersigned represent and warrant that they are duly authorized to bind their respective parties, that the facts set forth in this Change Order are true and complete to the best of their knowledge, and that execution of this Change Order will result in a binding amendment to the Contract as specified above.

Client:

By:

Date:

Service Provider:

By:

Date:

What the Project Management Contract Change Order Request Is

The Project Management Contract Change Order Request is a formal written amendment used to record proposed modifications to an existing project contract. It identifies the original agreement, describes the change in scope, sets out any cost or schedule adjustments, and requests written authorization from the contracting parties. Properly executed change orders create an auditable link between revised deliverables, payment terms, and revised milestones, helping teams manage scope, control costs, and reduce disputes by documenting who approved each modification and when.

Why a Standardized Change Order Request Matters

A standardized Change Order Request reduces ambiguity, creates a clear approval trail, and minimizes disputes by documenting scope, cost, and schedule changes. It supports invoicing, auditability, and consistent project governance across stakeholders.

Typical Users and Approvers

Typical users who prepare or approve change orders include project managers, contractors, and client representatives involved in scope management.

Project managers controlling scope, schedules, and resource allocation across phases.
General contractors and subcontractors documenting cost and time impacts of changes.
Owners, clients, and procurement officers authorizing budget modifications and approvals.

Signatures from authorized signers complete the request and confirm acceptance of the revised terms here.

Step-by-Step: Complete and Approve a Change Order Request

Follow this sequence to complete, approve, and archive a Change Order Request with recorded authorization and audit details.

01

Prepare Request: Reference original contract and include change description.
02

Calculate Impact: Itemize costs, time adjustments, and total delta.
03

Route for Approval: Send to authorized approvers with supporting documents.
04

Finalize & Archive: Obtain signatures, record date, distribute executed copy.

Essential Elements of a Professional Change Order Request

A professional Change Order Request contains clear identifiers, concise change descriptions, cost calculations, schedule impacts, approval fields, and locations for signatures and attachments.

Contract Reference

Include contract title, effective date, parties, and original contract number so reviewers can link the change order directly to the governing agreement and avoid misapplication of changes.

Scope Description

Clearly define which tasks, deliverables, or services are added, removed, or altered, and reference any affected contract sections to reduce ambiguity and disputes.

Cost Breakdown

Provide a line-item cost schedule showing labor, materials, markups, allowances, and taxes with calculation methods and whether figures are estimated or fixed prices.

Schedule Impact

Specify new milestones, float adjustments, critical-path effects, and revised completion dates along with any acceleration or time extension rationale and any mitigation steps to minimize delay impacts on downstream tasks.

Approvals Section

Include printed name, title, signature block, date, and an explicit approval checkbox or statement for each required party to prevent unauthorized acceptance and reference any delegated authority.

Attachments & Evidence

Attach estimates, drawings, change logs, correspondence, and any third-party approvals; label each exhibit and reference it in the main description to maintain auditability and simplify future reviews.

How the Change Order Workflow Moves from Draft to Archive

This workflow outlines actions from drafting through execution and distribution of the approved change order.

Draft: Prepare change text and compile supporting documents.
Review: Route to stakeholders for comment and cost verification.
Approve: Obtain signatures from authorized signatories.
Distribute: Send executed copy to archive and affected parties.

Digital Workflow Configuration for Online Change Orders

Configure a digital workflow to collect approvals, authenticate signers, and capture an audit trail before archiving the executed change order.

Field	Configuration
Signer authentication	Email link with optional SMS code
Signature type	Typed name or drawn signature allowed
Routing order	Sequential routing with conditional approver
Retention	Store signed PDF plus audit trail for retention

Distribution Methods and Platform Requirements

Digital delivery options and integrations determine how you share and authenticate the change order across teams and systems.

Supported Formats: PDF and Word DOCX supported
Integrations: Salesforce, NetSuite, Procore and Teams
Authentication Options: Email, SMS, KBA, SSO

Security and Compliance Checklist for Electronically Executed Change Orders

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

Audit Trail: Timestamps, IP address, action log, completion certificate

HIPAA: BAA available; protects PHI

ESIGN / UETA: Compliant with ESIGN and UETA

SOC 2 / ISO: SOC 2 Type II and ISO 27001 certified

Access Controls: SSO, SAML, and 2FA options available

Penalties and Risks from Incorrect or Incomplete Change Orders

Unauthorized Work: Claims, non-payment, dispute risk.

Late Approval: Schedule delays and liquidated damages.

Incorrect Amounts: Overpayment or underbilling exposure.

Tax Implications: Misreported costs affect tax filings.

Contract Breach: Termination or indemnity claims possible.

Notarization Errors: State invalidation or enforceability issues.

Common Preparation Pitfalls to Avoid

Vague change descriptions that fail to specify deliverables, making it hard to determine what work is included and leading to disputes over scope and payment.
Missing contract reference or incorrect contract number prevents linkage to the governing agreement and delays review and processing by contract administrators.
Failure to attach cost backup, drawings, or approvals forces reviewers to request additional documents and slows approval cycles, increasing project float consumption.
Not confirming required witnesses or notarization in the relevant jurisdiction can invalidate signatures or create enforceability disputes later.

How Change Order Requests Differ from Contract Amendments

Comparing document types clarifies the right approach: use the change order for execution-phase adjustments and amendments for formal contract-term modifications.

Document Type	Change Order Request	Contract Amendment
Scope	specific tasks/deliverables	contract-wide provisions
Approval Level	project-level approval	executive/legal approval
Timing	during project execution	may modify original terms
Legal Effect	limited to scope change	alters contract obligations

eSignature Pricing and Feature Overview for Change Order Workflows

Compare basic pricing and key features across common eSignature vendors to evaluate cost and compliance for processing change orders electronically.

	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	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	Yes
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently Asked Questions and Practical Answers

Practical answers to frequent questions about preparing, signing, and enforcing Project Management Contract Change Order Requests.

Need help? Contact support

Can a change order be signed electronically?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA (adopted by most states), so Change Order Requests may be e-signed. Exceptions include wills, court filings, and other statutorily excluded document types under ESIGN/UETA.
Recommended signer authentication methods
Use at least email verification plus one stronger method (SMS code, SSO, or KBA) for higher-risk changes; add signer identity, intent, and consent evidence to meet the ESIGN four‑part test (intent, consent, attribution, retention). Use 2FA for regulated workflows.
Notarization or witness requirement
Most change orders do not require notarization or witnesses; however, state law may require notary acknowledgement or witness signatures for certain real estate or power-of-attorney related amendments. Check relevant state rules and RON availability; when required, retain notary journal and A/V recording as applicable.
Storage and retention guidance
Store executed change orders as read-only PDFs with retained audit trails. Keep originals for the contract term plus at least three years; follow IRS recordkeeping (IRC §6501(a)) and HIPAA six-year rules (45 CFR §164.530(j)) when applicable. Use encrypted storage and access controls.
Common preparation mistakes
Unclear scope language, missing cost backup, incorrect effective dates, inconsistent party names, and absent approvals are frequent issues; they delay processing, risk non-payment, and can complicate audits and dispute resolution.
HIPAA and eSignature use
Yes for PHI transactions provided the eSignature vendor signs a Business Associate Agreement and technical safeguards are in place. HIPAA requires administrative, physical, and technical protections; retention follows 45 CFR §164.530(j). Confirm vendor HIPAA compliance and execute a BAA before transmitting PHI.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now