A PCO is a formal project change request documenting scope, cost, and schedule impacts. It provides contractual notice and forms the basis for negotiation and approval. Properly executed PCOs include identifiers, supporting backup, and authorized signatures to establish entitlement and auditability.

Are electronic signatures legally valid?

Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted by most states), electronic signatures are legally valid when intent, consent, attribution, and record retention are present. Confirm contract or statutory exceptions; some documents and court filings remain excluded.

Who has authority to sign a PCO?

Authorized signers are defined by the contract and organizational delegations of authority. Typically project managers, contractors’ authorized representatives, and owners’ procurement or contract officers sign PCOs. Verify signature authority limits to avoid invalid approvals or payment disputes.

What supporting attachments should I include?

Include RFIs, revised drawings, vendor quotes, subcontractor bids, cost worksheets, time-impact analyses, photos, and correspondence that justify scope and pricing. Reference attachments in the PCO body and ensure files are legible; incomplete backup is a common cause for rejection.

How long should I retain PCO records?

Retain PCO records for the project duration and for an extended period after closeout. Follow federal baselines: IRS records three years (IRC §6501(a)) and HIPAA six years (45 CFR §164.530(j)). Many organizations retain seven years or more for claims protection.

Can I revoke or cancel a PCO?

You may withdraw or cancel a PCO before owner acceptance following contract notice rules; after acceptance the change becomes part of the contract and requires a signed change order or amendment to reverse. Document withdrawals and retain timestamps to avoid disputes.

Electronic Signature
Templates
Project Management
Project Management PCO Document

Project Management PCO Document

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

Project Change Order (PCO)

Project Identification

Project Title:

Project ID: Client Name:

Client Address Project Manager

PM Contact Email: PM Phone:

PCO Identification

PCO Number: Date Submitted:

Submitted By (Requesting Party)

Requesting Department/Company:

Type and Priority of Change

Indicate applicable categories (check all that apply):

Change in scope Schedule adjustment Cost revision Emergency / Safety-critical

Description of Proposed Change

Summary of Change Reason for Change Items Specifically Added to Scope Items Specifically Removed or Out of Scope

Deliverables and Acceptance Criteria

Deliverables (describe each deliverable affected) Acceptance Criteria

Schedule Impact

Current Contract Start Date: Current Contract End Date:

Proposed New Completion Date: Net Calendar Days Added (if any):

Milestones Affected

Cost Impact and Payment

Provide detailed cost elements below. Costs shall be supported by substantiating documentation upon request.

Labor Cost Materials & Equipment Cost Subcontractor Cost Other Direct Costs Total Proposed Cost Adjustment (Sum of above) Proposed Payment Schedule

Evaluation and Approval Recommendation

Recommended Disposition: Approve Reject Defer / Require Revision

Evaluator Comments

Terms, Representations and Legal Provisions

Effect of Approval: Upon written approval and execution by authorized representatives of both parties, this PCO amends the contract only to the extent expressly set forth herein. No work associated with this PCO shall proceed for payment or schedule relief unless this PCO is fully executed by both parties or the parties otherwise issue a separate written authorization.

Cost Determination: Proposed costs are to be substantiated by time records, invoices, vendor quotes, or other documentation. Adjustments to the Contract Sum shall be limited to reasonable direct costs, plus any contractually allowed overhead and profit as specified in the contract. Taxes and duties imposed by law shall be borne as provided in the contract.

Schedule Adjustment: Any extension of time granted pursuant to this PCO will be limited to the net critical-path delay demonstrated by the Contractor and approved by the Owner. Acceleration required to mitigate such delay shall be subject to separate agreement as to costs and schedule.

No Waiver; Continuing Obligations: Approval of this PCO shall not constitute a waiver of any rights under the contract, nor relieve the Contractor of any continuing obligations, warranties, or performance requirements unless expressly stated. All other terms and conditions of the contract remain in full force and effect.

Notice and Claims Procedure: Any claim for additional compensation or time not set forth in this PCO must be submitted in accordance with the contract's notice and claims provisions. This PCO does not prejudice those contractual procedures for other claims.

Confidentiality: Information exchanged in connection with this PCO that is designated confidential shall be held in confidence and used only for evaluation and performance of this change, except as otherwise required by law.

Governing Law: This PCO shall be governed by and construed in accordance with the substantive laws applicable to the underlying contract. The parties submit to the exclusive dispute resolution procedures specified in the contract.

Additional Provisions or Notes

Certifications

The undersigned represent and warrant that they are authorized to submit and certify the information contained herein and that, to the best of their knowledge, the cost and schedule impacts are accurate and based on current information. Submission of this PCO does not constitute acceptance of the change by the other party unless expressly approved in writing.

Service Provider Certification (name and title) Client Certification (name and title)

Client:

By:

Date:

Service Provider:

By:

Date:

What the Project Management PCO Document Is

The Project Management PCO Document records proposed changes to a project’s scope, schedule, or cost and serves as the formal notice and request for evaluation under contract terms. It identifies the initiating party, describes the change in technical detail, itemizes labor and material cost impacts, and calculates any schedule adjustments or critical-path effects. The document creates a traceable record used during negotiation, approval, and back-charge processes, and supports claims or audits by linking attachments such as drawings, RFIs, and cost substantiation. Use consistent numbering, version control, and date stamps to maintain an auditable chain.

Why a Clear PCO Document Matters

A Project Management PCO Document clarifies scope changes, quantifies financial and schedule impacts, and documents approvals to reduce disputes. Clear PCOs establish contractual notice, support accurate change order pricing, and preserve entitlement when disputes or claims arise during project delivery.

Who Prepares and Reviews PCOs

Project managers, contractors, architects, owners, and construction administrators use Project Management PCO Documents to register and process scope or schedule changes consistently.

Project Managers: prepare PCOs, coordinate cost estimates, and submit for approval per contract procedures.
Contractors/Subcontractors: document proposed work, attach pricing backup, note schedule impacts, and follow notice clauses.
Owners/Clients and Architects: review PCOs, approve changes, and record budget or scope adjustments.

Properly completed PCOs improve transparency across bidding, change negotiation, payment approval, and project closeout processes, reducing administrative friction and claim exposure.

Essential Parts of a Professional PCO

A professional PCO includes identifiers, clear descriptions, quantified impacts, supporting attachments, approval routes, and version control to ensure traceability and enforceability.

Identification

Project name, PCO number, date, initiating party, and contract reference; consistent identifiers link the PCO to procurement, schedules, and billing records for auditability and revision history.

Change Description

Concise technical description of work changed, affected drawings or specifications, and reason for change; avoid ambiguous language to reduce interpretation disputes and expedite review and approval.

Cost Impact

Line-item labor, material, equipment, subcontract and overhead costs with unit rates, quantities, and a total change order amount; include backup estimates and vendor quotes for verification.

Schedule Impact

Identify duration changes, float consumption, critical path effects, and proposed mitigation measures; present a revised schedule or time-impact analysis to support approval and resource reassignment details.

Approvals

Signature block for authorized approvers, with their title, organization, date, sequential approval routing, and digital signature timestamps for auditability.

Attachments

Attach RFIs, revised drawings, cost backup, photos, and correspondence; reference attachments within the PCO and include cost comparison spreadsheets so reviewers can verify scope and cost claims.

Step-by-Step: Preparing and Filing a PCO

Follow these sequential steps to prepare, submit, and close a PCO with a clear audit trail and supporting evidence.

01

Prepare PCO: Gather scope, drawings, and cost backup; draft concise description.
02

Attach Evidence: Include RFIs, vendor quotes, cost worksheets, and photos where relevant.
03

Submit to PMO: Send through contract-defined routing or electronic workflow with version control.
04

Track Decision: Record approval, rejection, or requested changes and update schedule/cost records.

Where to Send and How Routing Works

Routing and submission depend on contract clauses and organizational workflow; electronic workflows reduce handling time and centralize records for audit.

Internal PMO: PMO reviews, assigns PCO numbers, and coordinates technical evaluation.
Contractor: Submits cost estimate and sequencing impacts; negotiates pricing with owner.
Owner/Client: Evaluates cost, schedule, and risk before accepting or rejecting the change.
Document Archive: Store final PCO, approvals, and attachments in project record system.

Configuring an Online PCO Workflow

Configure an online PCO workflow to capture fields, route approvals, and retain an audit trail for each change request.

Field	Configuration
Template	Pre-fill standard sections and numbering scheme
Conditional Logic	Show cost fields only when change estimate present
Approval Routing	Route by role with sequential or parallel approvals
Authentication	Use email, SMS code, or stronger methods for signer ID

Digital Submission: Platform Requirements

Ensure the e-signature platform supports the file formats, integrations, and authentication methods your project requires.

Integrations: Salesforce, NetSuite, Procore, Microsoft 365 supported
File Formats: PDF, DOCX, Excel, and image attachments
Authentication: Email, SMS code, KBA, SSO options

Security and Compliance Considerations

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

Certifications: SOC 2 Type II, ISO 27001, PCI DSS

HIPAA: BAA available for covered entities

Audit Trail: Complete timestamped activity log

Access Control: Role-based permissions and SSO

Authentication: Multi-factor options and identity proofing

Common Mistakes to Avoid

Incomplete cost backup leads to rejected PCOs and undermines entitlement, increasing negotiation time and potential disputes.
Late notice or missed contractual notice deadlines can forfeit entitlement to time or money under many construction contracts.
Ambiguous change descriptions without drawing references increase interpretation risk and may lead to scope creep.
Failure to route approvals or retain signed versions causes audit failures and weakens claims during disputes.

Risks and Consequences of Deficient PCOs

Cost Overruns: Unapproved charges borne by contractor

Schedule Delay: Liquidated damages potential

Payment Withholding: Owner may withhold funds

Contract Breach: Risk of termination or claims

Audit Exposure: Incomplete records trigger scrutiny

Legal Fees: Dispute resolution costs increase

Baseline eSignature Vendor Comparison for PCO Workflows

Compare baseline pricing and core features for common eSignature providers relevant to PCO workflows; signNow is listed first for vendor comparison.

	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	Yes (Premium)	Yes	Yes	Yes	No
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

Typical Timelines and Review Deadlines

Timelines depend on contract notice clauses; follow specified submission windows and internal review SLAs to preserve change entitlements.

Notice Deadline:

Submit change notice per contract; common range is 7–30 days

Owner Review:

Owners typically respond within their defined review period, often 10–30 days

Cost Validation:

Allow time for price checks, vendor quotes, and procurement review

Schedule Assessment:

Perform time-impact analysis promptly to quantify delay risk

Final Approval:

Record approvals or rejections with timestamps and retain signed PCOs

Milestone Sequence for a PCO Lifecycle

Key milestone sequence for a typical PCO lifecycle, from initiation through implementation and closeout with responsibilities at each stage.

01

Submission

Initiator files PCO with description, cost, and schedule impacts.

02

Technical Review

Engineers and discipline leads assess scope and impact within allocated review window.

03

Commercial Review

Cost team verifies estimates, procurement requests quotes, and prepares pricing.

04

Implementation

Approved changes are scheduled, issued to field, and tracked in change logs.

Examples: How Organizations Use PCO Workflows

Real-world examples show how digital change order workflows reduce turnaround and improve customer experience across property and project management firms.

Optica Ventures — Brian Fitzgibbons

Optica Ventures leveraged digital signing to manage investor and vendor approvals across projects when in-person signing was impractical.

Result: faster turnaround and simpler customer workflows.
Brian Fitzgibbons said the interface is simple and easy-to-use for the team; more importantly, it is just as easy for customers, enabling remote approvals without sacrificing documentation or traceability during audits.

Martin Properties — Tim Martin

Martin Properties uses online PCO workflows to finalize lease and construction change approvals while staff work remotely or onsite.

They achieved compliant execution across devices.
Tim Martin noted he can process and execute documents online with full compliance and security, and that mobile signing enabled faster turnaround and reduced the need for paper handling across properties.

Frequently Asked Questions About PCO Documents

These FAQs address common questions about preparing, signing, and managing Project Management PCO Documents, including eSignature legality and typical contract controls.

Need help? Contact support

What is a PCO?
A PCO is a formal project change request documenting scope, cost, and schedule impacts. It provides contractual notice and forms the basis for negotiation and approval. Properly executed PCOs include identifiers, supporting backup, and authorized signatures to establish entitlement and auditability.
Are electronic signatures legally valid?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted by most states), electronic signatures are legally valid when intent, consent, attribution, and record retention are present. Confirm contract or statutory exceptions; some documents and court filings remain excluded.
Who has authority to sign a PCO?
Authorized signers are defined by the contract and organizational delegations of authority. Typically project managers, contractors’ authorized representatives, and owners’ procurement or contract officers sign PCOs. Verify signature authority limits to avoid invalid approvals or payment disputes.
What supporting attachments should I include?
Include RFIs, revised drawings, vendor quotes, subcontractor bids, cost worksheets, time-impact analyses, photos, and correspondence that justify scope and pricing. Reference attachments in the PCO body and ensure files are legible; incomplete backup is a common cause for rejection.
How long should I retain PCO records?
Retain PCO records for the project duration and for an extended period after closeout. Follow federal baselines: IRS records three years (IRC §6501(a)) and HIPAA six years (45 CFR §164.530(j)). Many organizations retain seven years or more for claims protection.
Can I revoke or cancel a PCO?
You may withdraw or cancel a PCO before owner acceptance following contract notice rules; after acceptance the change becomes part of the contract and requires a signed change order or amendment to reverse. Document withdrawals and retain timestamps to avoid disputes.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now