Can I sign a PCO electronically?

Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and the Uniform Electronic Transactions Act (UETA) where adopted, provided the transaction shows signer intent, consent to electronic records, attribution to the signer, and a reproducible record.

What makes an e-signature legally valid?

A valid e-signature satisfies four elements: intent to sign, consent to transact electronically, attribution to the identified signer, and retention of an accurate record that can be reproduced. Consumer-facing financial or healthcare records also require ESIGN consumer disclosures.

Are notarizations required for PCOs?

Not generally. Most PCOs are internal contract amendments and do not require notarization. If a contract or state statute requires authentication or if parties want evidentiary assurance, use in-person notarization or Remote Online Notarization (RON) with retained audio-video, where permitted.

Who can sign on behalf of a company?

Only persons with delegated authority can bind the company. Verify corporate resolutions, procurement delegations, or contract signature blocks; capture printed name, title, and date with each signature to document authority for audits or disputes.

How should disputed PCOs be handled?

Follow the contract dispute procedure: preserve supporting documents, send written notices within contract-specified timeframes, and escalate per the agreement (e.g., mediation). Maintain version history and communications to support any later claims or resolution processes.

How long must I keep PCO records?

Retain PCOs per applicable retention rules: at least 3 years for tax-related records (IRC §6501(a)), 6 years for HIPAA-related records (45 CFR §164.530(j)) where applicable, and commonly 7–10 years for contract dispute risk; state law may require longer retention.

Business PCO Document

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

BUSINESS PCO DOCUMENT (CHANGE ORDER)

This Business PCO Document (the "Change Order") is made effective as of , by and between the parties identified below.

Parties

Party A (Contractor) Name: Party A Address: Party B (Client) Name: Party B Address:

Recitals

WHEREAS, Party A and Party B entered into a principal agreement entitled "Original Contract" dated , (the "Agreement"), pursuant to which Party A agreed to perform certain services.

WHEREAS, the parties have agreed that changes to the scope, schedule, and/or compensation under the Agreement are necessary and desirable, and the parties wish to document the agreed modifications in this Change Order.

Scope of Work

Description of Change (Scope of Work):

Payment Terms

Total Change Order Amount (USD): Payment Schedule and Milestones: Late Payment Fee:

All invoices submitted under this Change Order shall reference this Change Order number and shall be payable in accordance with the Payment Schedule above. Interest on past-due amounts shall accrue at the rate specified in the Late Payment Fee field, or if no rate is specified, at the maximum rate permitted by law.

Term and Termination

This Change Order shall become effective on the Start Date: , and shall continue until the Completion Date: , unless earlier terminated as provided herein.

Notice Period for Termination (days):

Either party may terminate this Change Order for material breach by the other party if the breach remains uncured after the Notice Period specified above. Termination shall not relieve either party of obligations that accrued prior to the effective date of termination.

Confidentiality

Each party acknowledges that in connection with this Change Order it may receive Confidential Information of the other party. "Confidential Information" means non-public business, technical, financial or other information disclosed in any tangible or intangible form and identified as confidential or which, under the circumstances, reasonably should be understood to be confidential. Each party shall: (a) protect Confidential Information with at least the same degree of care it uses to protect its own confidential information, but no less than reasonable care; (b) use Confidential Information only to perform obligations under this Change Order; and (c) not disclose Confidential Information to any third party except to its employees, consultants or contractors who have a need to know and are bound by confidentiality obligations no less protective than those hereunder. Upon termination or request, the receiving party shall promptly return or destroy the disclosing party's Confidential Information and certify such return or destruction in writing.

Governing Law

This Change Order shall be governed by and construed in accordance with the laws of the State of without regard to its conflict of law principles. The parties submit to the exclusive jurisdiction of the state and federal courts located in that State for any action arising under or relating to this Change Order.

Entire Agreement; Modification

This Change Order, together with the Agreement and any documents expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings and communications, whether written or oral. No amendment, modification or waiver of any provision of this Change Order shall be effective unless in writing and signed by authorized representatives of both parties.

Notices

All notices required or permitted under this Change Order shall be in writing and delivered to the addresses below:

Notice to Party A - Contact Name: Notice to Party A - Address: Notice to Party B - Contact Name: Notice to Party B - Address:

Authorization

The undersigned representatives of the parties each certify that they are duly authorized to execute this Change Order on behalf of their respective principals and that execution of this Change Order shall bind their principals to the terms set forth herein.

Party A - Printed Name:

By:

Date:

Party B - Printed Name:

By:

Date:

What the Business PCO Document Is and When It’s Used

The Business PCO Document (Potential Change Order) is a formal written record used to propose and document changes to a commercial contract’s scope, price, or schedule. Common in construction and other project-based engagements, a PCO describes the proposed amendment, estimates cost and time impacts, assigns responsibility, and records approval or rejection by authorized parties. Once accepted, it serves as the basis for contractual modification, billing adjustments, and schedule updates. Accurate PCOs reduce ambiguity and create an auditable trail for claims, invoicing, and project controls.

Why a Clear Business PCO Document Matters

A precise Business PCO Document clarifies proposed scope and cost impacts, identifies approval authority, and creates an evidentiary record to support invoicing and claims. It reduces ambiguity, shortens approval cycles, and limits exposure to disputes when paired with consistent version control and properly authenticated signatures.

Who Typically Prepares and Reviews a PCO

Typical users include project managers, contractors, subcontractors, and procurement teams who manage contract changes on-site and in-office.

General contractors: issue and track PCOs, aggregate subcontractor costs, and seek owner approvals.
Project managers: evaluate change scope, estimate schedule impacts, and coordinate internal stakeholders.
Owners and clients: review cost and time changes, approve budget amendments, and manage payments.

Use PCOs to document decisions, preserve audit trails, and route approvals to designated signatories promptly.

Core Elements a Professional Business PCO Should Include

A complete Business PCO Document organizes the change request so reviewers can approve or reject it quickly and consistently.

Unique Identifier

Assign a PCO number for traceability across project records and invoices.

Effective Date

Specify when the change takes effect for schedule and billing purposes.

Scope Description

Concise description of work changed, referenced drawings, and affected contract clauses.

Cost Breakdown

Itemized labor, materials, overhead, taxes, and contingency amounts.

Schedule Impact

Estimated delay or acceleration in days and revised milestone dates.

Approval Block

Signatures, printed names, titles, dates, and any delegated authority notes.

Stepwise Process to Prepare, Route, and Finalize a PCO

Follow these steps to prepare, route, and record a Business PCO Document for review and approval.

01

Draft: Describe change, attach evidence, and estimate costs.
02

Internal Review: Validate scope and pricing with internal stakeholders.
03

Route for Approval: Send to authorized signatories in labeled order.
04

Record & Invoice: File signed PCO and update project budget and schedule.

How to Update or Revise an Existing PCO

Use this grid to manage PCO revisions, approvals, and re-issuance while maintaining clear version history.

01

Identify Revision:

Log reason and reference original PCO.

02

Update Document:

Edit scope, cost, and schedule fields.

03

Notify Stakeholders:

Email revised PCO to affected parties.

04

Re-approve:

Collect signatures from required approvers.

05

Archive Old Version:

Mark superseded documents and retain history.

06

Update Systems:

Adjust budget and schedule in project controls.

Online Workflow Settings for Automating PCO Routing

Configure online workflows to automate PCO routing, conditional approvals, and retention, reducing manual steps and errors.

Field	Configuration
Signature Placement	Place signature and date fields where approval occurs.
Conditional Approval	Trigger additional approver if cost exceeds threshold.
Authentication	Use email link, SMS code, or KBA for signer identity.
Reminders & Expiry	Set reminders and expiration to enforce timely responses.

Typical Routing: From Proposal to Archive

This flow shows typical routing: creation, review, signature, and filing for a Business PCO Document.

Create: Originator completes form and attaches supporting documents.
Review: Stakeholders review technical and cost impacts.
Sign: Authorized parties sign electronically or in ink.
Archive: Store final document in project records and accounting.

Technical Considerations for Digital PCO Workflows

Choose platforms and integrations that support eSignature, document storage, and audit trails for Business PCO Document workflows.

File Formats: Supports PDF, DOCX, and Excel exports.
Integrations: Connect to ERP, CRM, and cloud storage.
Authentication: Email link, SMS code, SSO options.

Vendor Pricing and Feature Snapshot for eSignature Tools

Compare eSignature vendor features and starting prices to evaluate platforms for executing and tracking Business PCO Documents at scale.

	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, no credit card required	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
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
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Real-World Examples of Electronic PCO Workflows

Two customer examples illustrate how online signing and standardized PCOs improve document handling across projects.

Optica Ventures LLC

Optica Ventures used an eSignature workflow to shorten subcontractor approvals for change orders across multiple projects.

Mobile signing reduced field approval delays.
"The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers." The approach improved consistency in PCO documentation and centralized audit trails.

Martin Properties

A property development firm moved PCO approvals online to avoid site delays and paper routing.

Field approvals completed from mobile devices.
"I can process and execute all of these documents online with 100% compliance and built-in security." This enabled faster budget updates and clearer records for accounting.

Common Mistakes to Avoid When Preparing a PCO

Incomplete scope descriptions: Vague or partial descriptions force rework, delay approvals, and weaken enforceability; always reference contract clause numbers, drawings, and affected line items.
Underestimating cost impact: Omitting labor burden, taxes, or contingency leads to disputed invoices; provide a line-item breakdown and unit rates to avoid misunderstandings.
Wrong signer or lack of authority: Signatures by unauthorized personnel can invalidate approvals; confirm delegated authority and capture title, printed name, and date with each signature.
Poor version control: Overwriting previous PCOs without change logs causes confusion and audit gaps; maintain a revision history and reference prior related PCO numbers.

Key Risks and Consequences of Deficient PCOs

Contract Disputes: Increased risk of claims and litigation.

Delayed Payments: Invoices may be rejected or delayed.

Tax Reporting: Inaccurate records affect deductions; see IRC §6501(a).

Audit Exposure: Missing audit trail raises compliance risk.

Invalid Approvals: Unauthorized signatures can nullify changes.

Mechanic's Liens: Unresolved changes may trigger lien claims.

Who Can Sign and What Authority Looks Like

Project Manager

Typically authorized to approve technical scope changes within delegated financial limits. Their signature confirms schedule and resource impacts, but larger cost increases often require secondary financial approval; record title and contact information for audit purposes.

Contracting Officer

An officer or procurement representative authorized by contract to approve price changes and bind the organization. Confirm authority via corporate resolution or delegated authority matrix and capture printed name, title, and date to validate signatures.

Dates and Deadlines to Track for Each PCO

Key PCO deadlines affect notice, approval windows, and invoice timing; calendar these dates to preserve claims and ensure timely payment.

Notice Deadline:

Provide written notice per contract within the specified timeframe to preserve claims.

Approval Window:

Response timing is contract-specified and varies; confirm the exact term in the agreement.

Invoice Submission:

Submit supporting invoices per billing cycle and reference the related PCO number.

Dispute Notice:

File formal dispute per contract procedures within any contractual timeframe.

Record Retention Start:

Retention periods begin on the effective date or acceptance date, per policy.

Milestones: From Proposal to Accounting Update

Milestones from PCO proposal through acceptance and accounting update provide a sequential path and assigned responsibilities.

01

Stage One: Proposal

Originator issues PCO with supporting documents.

02

Stage Two: Evaluation

Technical and cost review occurs.

03

Stage Three: Approval

Authorized signatory accepts or rejects the change.

04

Stage Four: Implementation

Update schedules, budgets, and invoice accordingly.

Frequently Asked Questions About Business PCO Documents

Answers to common legal, procedural, and technical questions about preparing, signing, and storing PCOs.

Need help? Contact support

Can I sign a PCO electronically?
Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and the Uniform Electronic Transactions Act (UETA) where adopted, provided the transaction shows signer intent, consent to electronic records, attribution to the signer, and a reproducible record.
What makes an e-signature legally valid?
A valid e-signature satisfies four elements: intent to sign, consent to transact electronically, attribution to the identified signer, and retention of an accurate record that can be reproduced. Consumer-facing financial or healthcare records also require ESIGN consumer disclosures.
Are notarizations required for PCOs?
Not generally. Most PCOs are internal contract amendments and do not require notarization. If a contract or state statute requires authentication or if parties want evidentiary assurance, use in-person notarization or Remote Online Notarization (RON) with retained audio-video, where permitted.
Who can sign on behalf of a company?
Only persons with delegated authority can bind the company. Verify corporate resolutions, procurement delegations, or contract signature blocks; capture printed name, title, and date with each signature to document authority for audits or disputes.
How should disputed PCOs be handled?
Follow the contract dispute procedure: preserve supporting documents, send written notices within contract-specified timeframes, and escalate per the agreement (e.g., mediation). Maintain version history and communications to support any later claims or resolution processes.
How long must I keep PCO records?
Retain PCOs per applicable retention rules: at least 3 years for tax-related records (IRC §6501(a)), 6 years for HIPAA-related records (45 CFR §164.530(j)) where applicable, and commonly 7–10 years for contract dispute risk; state law may require longer retention.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now