Is an e-signed CO legally binding?

Yes, electronic signatures satisfy the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted if the four-part validity test is met: intent, consent, attribution, and record retention. Confirm no statutory exception applies to the specific transaction.

When is notarization required for a CO?

Notarization is rarely required for internal change orders but may be mandated by contract or for changes affecting legal descriptions, property, or liens. For RON and state-specific requirements, consult the state notary commission or contract terms before execution.

Who has authority to sign the change order?

Authorized signers are those granted signature authority in the original contract or internal delegation policies. Typical signers include project managers, procurement officers, finance approvers, or client representatives with explicit authority. Verify delegate authority to avoid invalid approvals.

How do I correct errors after signing?

If a signed change order contains errors, prepare a corrective amendment or a new change order that references the original number and explains corrections. Obtain approvals and re-signatures from the same authorized parties and record the reason for amendment.

Are there state-by-state differences to consider?

Yes. Notarization, witness requirements, and RON availability vary by state. ESIGN governs interstate transactions while UETA applies in most states; New York follows ESRA. Consult the state Secretary of State or legal counsel for jurisdictional nuances before relying on a specific execution method.

How long must I retain executed change orders?

Retain executed change orders for the full term of the contract plus at least three years. For tax or financial records follow IRC §6501(a) minimums; for healthcare records follow HIPAA six-year retention. Adjust for longer state-specific requirements and legal holds.

Electronic Signature
Templates
Project Management
Project Management Support CO

Project Management Support CO

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

PROJECT MANAGEMENT SUPPORT CHANGE ORDER (CO)

Project Identification

Project Title:

Project ID: Client Name:

Service Provider: Project Manager:

Original Statement of Work Date: Original SOW Reference ID or Section:

Recitals

This Change Order amends the Statement of Work identified above and incorporated into the Agreement between Client and Service Provider. Upon execution by authorized representatives of both parties, the terms set forth in this Change Order shall modify the original SOW to the extent specified herein.

Change Order Summary

Change Order Title Change Order Justification

Scope of Work (Added / Modified)

Detailed Scope of Work Out-of-Scope Items (remain excluded)

Deliverables and Acceptance Criteria

Deliverable 1 Title:

Deliverable 1 Description Deliverable 1 Acceptance Criteria

Deliverable 2 Title:

Deliverable 2 Description Deliverable 2 Acceptance Criteria

Timeline and Milestones

Proposed Change Order Start Date: Proposed Change Order End Date:

Milestone 1

Due Date:

Milestone 1 Description

Budget, Fees, and Payment

Total Change Order Cost (USD): Updated Estimated Total Project Cost (USD):

Cost Impact Breakdown Payment Schedule and Billing Terms

Pricing Basis: Time & Materials Fixed Price Not-to-exceed

Change Order Authorization and Process

This Change Order must be countersigned by authorized representatives of both parties to become effective. Work performed by Service Provider prior to full execution that is expressly authorized in writing by Client will be treated as work under this Change Order and will be invoiced in accordance with the Payment Schedule above.

Change Control and Document Reference

Confidentiality, Representations, and Warranties

Confidential Information disclosed in connection with this Change Order shall remain subject to the confidentiality obligations of the underlying Agreement. Each party represents that it has the authority to enter into this Change Order and that performance will not violate applicable law or third-party rights.

Service Provider warrants that services performed under this Change Order will be performed in a professional manner in accordance with industry standards. Except as expressly set forth herein, no additional warranties are made.

Limitation of Liability and Indemnification

Except as otherwise set forth in the Agreement, each party's liability arising from or related to this Change Order shall be limited in the same manner as set forth in the Agreement. Each party agrees to indemnify the other for third-party claims arising from that party's breach or negligence in performing this Change Order.

Governing Law and Dispute Resolution

This Change Order shall be governed by and construed in accordance with the laws of:

Notice Contacts for This Change Order

Client Contact Service Provider Contact

Additional Terms

Additional Provisions

Authorization and Signatures

Client Printed Name:

By:

Date:

Service Provider Printed Name:

By:

Date:

What the Project Management Support CO Is

Project Management Support CO is a standardized change order form used to document approved modifications to project scope, schedule, budget, or deliverables for an active engagement. It records a clear description of the change, the reason, and the quantified impact on cost and time, plus required stakeholder approvals. The completed form creates a traceable record for invoicing, accounting, and project governance. When executed electronically with compliant e-signatures, it serves as a legally enforceable amendment to the original agreement under applicable U.S. e-signature law.

Why a Formal Change Order Matters

Project Management Support CO helps formalize approved changes, reduce disputes, and align stakeholder expectations. It clarifies cost and schedule impacts and establishes signatory authorization for amended work. Using a consistent form improves auditability and reduces downstream billing or scope disagreement.

Who Typically Completes This Change Order

Common users in the project lifecycle include procurement, project managers, contract administrators, client representatives, and other authorized stakeholders.

Project managers and PMO staff who approve scope and schedule adjustments.
Contract admins and procurement handling change pricing and purchase orders.
Clients or owners requiring documented consent before project work continues.

Proper routing ensures authorized signers approve modifications and that the change order is recorded with procurement and finance for billing and control.

Core Elements of a Professional Project Management Support CO

Core elements of a professional Project Management Support CO ensure clarity, accountability, and traceable approvals across technical, commercial, and scheduling dimensions.

Change Description

Provide concise, itemized description of the work being added, modified, or removed. Include reference to original contract section, technical specifications, and any relevant drawings or attachments.

Scope Impact

Detail how deliverables, acceptance criteria, or functional requirements change. State whether the change creates new tasks, modifies existing tasks, or removes prior obligations, and identify affected milestones.

Schedule Adjustment

Specify new start and completion dates, critical path changes, and any interim milestones. Include justification for the schedule shift and expected effects on downstream dependencies.

Cost Change

Itemize cost increases or decreases, with unit rates, quantities, labor hours, and material costs. Show subtotal, taxes, and the total net change to contract value with currency specified.

Authorization

List required approvers by role and provide signature blocks with printed name, title, organization, and date. Include conditional approvals if partial acceptance is permitted and contact details.

Change Rationale

Explain reason for change, risk mitigation measures, alternative options considered, and implications for warranties or guarantees. Tie rationale to project objectives, prior communications, and recorded approvals.

Required Information to Complete the CO

Change Order No.: Unique identifier for tracking.

Effective Date: MM/DD/YYYY format required.

Project Name: Full project title and ID.

Requester: Name, title, contact email.

Cost Impact: Net change in contract dollars.

Attachments: Reference drawings, specs, and estimates.

Step-by-Step: Complete and Approve the CO

Follow these sequential steps to complete and approve the Project Management Support CO accurately and on time.

01

Draft: Describe the change, attach supporting documents.
02

Estimate: Calculate cost and schedule impacts with line items.
03

Review: Route to stakeholders for technical and commercial approval.
04

Authorize: Obtain signatures and update contract records and logs.

How to Configure an Online Change-Order Workflow

Configure your online workflow to collect approvals, store backups, and capture an audit trail for the change order.

Field	Configuration
Signer Authentication	Email link or SMS code with optional KBA
Field Types	Signature, initials, date, conditional fields
Routing Order	Sequential or parallel signer routing based on role
Storage	PDF copy saved with audit trail metadata

Where to Send or File an Approved Change Order

After approval, distribute the executed change order to contract records, finance, and project delivery teams following employer procedures.

Procurement: File with procurement and link to purchase order.
Finance: Submit for invoicing and budget adjustment entries.
Project Team: Store in project repository and notify affected leads.
Client: Send executed copy to client contact for records.

Distribution Channels and Platform Requirements

Electronic submission supports email, secure portal, or integrated eSignature platforms for authenticated approvals and audit trails.

Formats Supported: PDF, DOCX, and editable form types.
Integrations: Connectors for NetSuite, Salesforce, Box, Procore.
Authentication: Email, SMS, SSO, or KBA options.

Typical Timelines and Deadlines for Change Orders

Typical timing and deadlines for a change order vary by contract terms; plan for internal review, client response, approval, and accounting updates.

Internal Review Window:

Allow 3 to 7 business days for technical and commercial checks.

Client Response Target:

Request client approval within 10 business days or per contract.

Effective Date Rule:

Use agreed effective date or date of last signature.

Accounting Update:

Post approved cost changes within the next billing cycle.

Dispute Escalation:

Escalate unresolved issues per contract dispute clauses.

Common Preparation Mistakes to Avoid

Failing to describe the change precisely leads to scope ambiguity, rework, and disagreements about deliverables and acceptance criteria.
Omitting cost breakdowns or supporting estimates causes late billing disputes and can trigger audit flags with finance.
Routing to incorrect approvers delays execution; verify signatory authority before sending for signature to avoid rejections.
Using inconsistent document versions or failing to attach referenced exhibits undermines enforceability and complicates recordkeeping.

Penalties and Risks from Incorrect or Unapproved Changes

Contract Breach: Unapproved work risks breach claims.

Payment Delay: Finance may withhold payments.

Audit Findings: Weak records can trigger audit findings.

Disallowed Costs: Costs rejected by client or auditor.

Project Delay: Unclear approvals extend timelines.

Liability Shift: Incorrect change language shifts liability.

eSignature Vendor Pricing Snapshot Relevant to Change Orders

Vendor pricing and feature availability for common eSignature duties. signNow column placed first to reflect verified plan and feature data.

	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 (Business Premium)	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions About the Project Management Support CO

Answers to common questions about completing, signing, and storing a Project Management Support CO in U.S. projects and electronic workflows.

Need help? Contact support

Is an e-signed CO legally binding?
Yes, electronic signatures satisfy the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted if the four-part validity test is met: intent, consent, attribution, and record retention. Confirm no statutory exception applies to the specific transaction.
When is notarization required for a CO?
Notarization is rarely required for internal change orders but may be mandated by contract or for changes affecting legal descriptions, property, or liens. For RON and state-specific requirements, consult the state notary commission or contract terms before execution.
Who has authority to sign the change order?
Authorized signers are those granted signature authority in the original contract or internal delegation policies. Typical signers include project managers, procurement officers, finance approvers, or client representatives with explicit authority. Verify delegate authority to avoid invalid approvals.
How do I correct errors after signing?
If a signed change order contains errors, prepare a corrective amendment or a new change order that references the original number and explains corrections. Obtain approvals and re-signatures from the same authorized parties and record the reason for amendment.
Are there state-by-state differences to consider?
Yes. Notarization, witness requirements, and RON availability vary by state. ESIGN governs interstate transactions while UETA applies in most states; New York follows ESRA. Consult the state Secretary of State or legal counsel for jurisdictional nuances before relying on a specific execution method.
How long must I retain executed change orders?
Retain executed change orders for the full term of the contract plus at least three years. For tax or financial records follow IRC §6501(a) minimums; for healthcare records follow HIPAA six-year retention. Adjust for longer state-specific requirements and legal holds.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now