Can a PCR be signed electronically?

Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA provisions, electronic signatures are generally valid for contracts and amendments unless a specific exception applies.

When is notarization required?

Notarization is seldom required for ordinary contract amendments, but it may be necessary when the change conveys real property or a statute or contract specifically requires an acknowledgement.

Who can sign a PCR for a company?

A PCR must be executed by a person authorized under the contract or corporate authority. If authority is unclear, attach a corporate resolution or POA showing delegated signing rights.

How should you store executed PCRs?

Store signed PCRs in a secure document repository as PDF/A or equivalent, preserve the audit trail, and retain per applicable retention rules (see IRS, HIPAA, and state requirements).

What if an approver refuses to sign?

Document the refusal and reason, escalate per the contract’s dispute or change governance clauses, and avoid implementing the change until approved to prevent breach claims.

Are click-to-sign approvals legally sufficient?

Click-to-sign can be sufficient if it demonstrates signer intent, consent to electronic transactions, attribution, and retention capability consistent with ESIGN/UETA requirements.

Electronic Signature
Templates
Miscellaneous
Project Change Request

Project Change Request

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

PROJECT CHANGE REQUEST

WHEREAS

WHEREAS, Client Name: and Contractor Name: previously entered into a services agreement governing the Project titled Project Name: .

WHEREAS, the parties desire to document and authorize a proposed change to the Work described in the Agreement and set forth the scope, cost, schedule impacts, and any modifications to the Agreement's terms by executing this Project Change Request.

Change Request Details

Change Request Title

Request Number:

Request Date:

Requested By Change Type (select all that apply)

Scope Schedule Budget Specification/Deliverable Other

Scope of Work

Provide a clear and detailed description of the change to the Work. Include deliverables, acceptance criteria, and any tasks added or removed. This description becomes an amendment to the Agreement upon approval.

Reason for Change

Impact Assessment

Estimated Cost Impact: $ (provide breakdown below)

Original Completion Date: Proposed Completion Date:

Schedule Impact Description

Payment Terms

If this change increases the contract price, the parties agree the Change Price shall be: $.

Payment Schedule / Milestones

Late Payment Fee: on overdue amounts, calculated from invoice due date.

Term and Termination

Effective Start Date for this Change: . Anticipated End Date:

Notice to terminate this Change Request must be provided in writing and delivered at least days prior to the intended termination date. Termination of the underlying Agreement will not be affected except as expressly modified herein.

Termination Consequences

Confidentiality

Each party shall maintain the confidentiality of Confidential Information disclosed in connection with this Change Request in accordance with the confidentiality provisions of the Agreement. Confidentiality obligations with respect to information exchanged under this Change Request shall survive for years following final payment or termination of the Agreement, unless a longer period is specified in the Agreement.

Governing Law

This Change Request shall be governed by and construed in accordance with the laws of the State of , without regard to its conflict of law principles.

Entire Agreement

Except as expressly modified by this Change Request, all terms and conditions of the Agreement remain in full force and effect. This Change Request, together with the Agreement, constitutes the entire understanding between the parties with respect to the subject matter herein and supersedes any prior oral or written representations, proposals, or agreements concerning the change.

Approvals and Authorizations

By signing below, the signatories represent and warrant that they are authorized to commit their respective parties to the terms of this Project Change Request and that the representations, scope, costs, and schedule set forth above are accurate to the best of their knowledge.

Requesting Party (Client)

Party Printed Name:

By:

Date:

Responding Party (Contractor)

Party Printed Name:

By:

Date:

What a Project Change Request Is and why it matters

A Project Change Request (PCR) is a formal written notice used to propose and record changes to a project’s scope, schedule, budget, or deliverables. It captures the requested change, the reason, a description of technical and commercial impacts, required approvals, and any attached supporting documents. The PCR becomes an official contract amendment when executed by authorized parties and is used to update project baselines, track approvals, and provide an audit trail for dispute resolution, financial accounting, and regulatory review.

Why documenting changes with a PCR reduces risk

A clear PCR centralizes change information, clarifies responsibilities, prevents scope creep, and preserves an auditable record of approvals and cost or schedule impacts to reduce later disputes.

Typical users and stakeholders for a Project Change Request

Project managers, contract administrators, and client representatives commonly prepare, review, and approve PCRs to control project changes.

Project managers — initiate requests, document scope detail, and propose mitigation steps for impacted tasks.
Contract administrators — evaluate commercial impact, update budgets, and ensure compliance with contract terms.
Clients/owners — review technical justification, authorize changes, and confirm budget or schedule acceptance.

Signed PCRs should be retained by project controls, procurement, and the client’s contract file for audit, financial tracking, and dispute resolution.

Essential sections to include in a professional Project Change Request

A complete PCR groups information so reviewers can quickly assess the change: concise summary, technical details, quantified impacts, approval routing, and supporting attachments to justify the modification.

Change Summary

One- or two-sentence description that states what is changing and why. This summary helps approvers assess urgency without reading full technical attachments.

Detailed Description

A precise description of the work to be added, removed, or altered, including affected deliverables, technical specs, and any assumptions or constraints that determine scope boundaries.

Cost Impact

A line-item estimate of direct and indirect costs, contingency, and who is responsible for funding. Include currency, basis of estimate, and any receivable or payable changes.

Schedule Impact

Quantify effects on milestones and completion dates, list affected tasks, and provide an updated critical-path summary showing any float or delay implications.

Approval Routing

List required approvers, their roles, and the order of review. Specify escalation rules when approvals are delayed or when approvals exceed delegated authority limits.

Attachments & Evidence

Include drawings, specifications, vendor quotes, photographs, or test reports that substantiate the change and support cost and schedule estimates.

How to prepare and route a Project Change Request

Follow a consistent sequence to minimize delays and ensure the request is actionable and auditable.

01

Draft the Request: Document the change, impacts, and attachments clearly.
02

Assess Impacts: Quantify cost, schedule, risk, and contract implications.
03

Obtain Approvals: Route to listed approvers in the defined order.
04

Implement and Record: Once signed, update baselines and archive the executed PCR.

Typical digital workflow settings for Project Change Requests

Configure routing and authentication to match your organization’s approval authorities and record-keeping policies.

Field	Configuration
Notification Method	Email with digest and reminder cadence
Approval Order	Sequential or parallel based on dollar thresholds
Storage Location	Project document repository with version control
Authentication	Email link, SMS code, or multi-factor for high-risk approvals

From request to execution — simplified flow

A concise end-to-end flow clarifies responsibilities and the moment when a change becomes effective.

Create PCR: Populate fields and attach evidence.
Send to Approvers: Notify listed approvers in required order.
Sign and Record: Approvers sign; system captures audit trail.
Update Baselines: Revise schedule and budget; archive executed PCR.

Technical considerations for digital PCRs and eSubmission

Choose formats, integrations, and authentication consistent with corporate IT and records policies.

Supported Formats: PDF and DOCX are preferred for redlines and signed archives.
Integrations: Connect to systems like Salesforce, NetSuite, or Box for traceability.
Signer Authentication: Use email, SMS, or stronger methods where required.

Ensure the chosen platform supports export, audit trails, and long-term archival formats aligned with legal and internal retention requirements.

Typical timing expectations for PCR processing

Set clear internal SLAs so teams know when to expect reviews and approvals; adjust for urgency and contract terms.

Submission Window:

Submit as soon as change is identified; earlier notice reduces cost and delay.

Initial Review:

Common target: 3–10 business days for technical and commercial review.

Cost Assessment:

Allow time for vendor quotes; 5–15 business days typical for external pricing.

Approval Turnaround:

Small changes: 24–72 hours; major changes: several business weeks.

Effective Date:

Specify whether change is retroactive, on signature, or on a stated future date.

Key milestones from request to closeout

A numbered milestone view helps stakeholders track progress and identify bottlenecks in the PCR lifecycle.

01

1. Request Submitted

Requestor files PCR with required documentation and IDs.

02

2. Impact Evaluation

Project controls and finance assess scope, cost, and schedule impacts.

03

3. Approval Decision

Designated approvers accept, reject, or request changes.

04

4. Implementation & Archive

Work proceeds per approved change; executed PCR is archived.

Common mistakes that delay or invalidate PCRs

Insufficient description — failing to state precise work leads to disputes and rework; include drawings and exact scope.
Missing cost breakdown — vague or absent cost estimates stall approvals and complicate budget reconciliation.
Incorrect approval routing — bypassing required signatories can void the amendment under the contract authority matrix.
Poor version control — circulating multiple untracked drafts produces confusion and undermines the official record.

Risks and potential consequences of flawed or unsigned PCRs

Contract Breach: Unapproved work may be treated as non‑contractual and expose the performing party to liability.

Delay Claims: Lack of approved schedule changes can trigger liquidated damages or disputed extensions.

Payment Disputes: Without an executed cost change, invoices may be withheld or rejected.

Audit Failures: Incomplete records can fail internal or external audits and harm compliance posture.

Regulatory Exposure: Public projects may require documented approvals for transparency and grant compliance.

Recordkeeping Gaps: Missing signed PCRs complicate dispute resolution and increase legal costs.

eSignature vendor comparison — pricing and core capabilities

Compare basic price points and capability signals to match platform features with PCR volume, authentication needs, and compliance obligations.

	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	Yes	Yes	Yes	Yes
Bulk Send	Yes	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 by plan	Varies by plan	Varies by plan

Frequently asked questions about Project Change Requests and eSigning

Answers to the most common practical and legal questions teams raise when preparing, signing, and storing PCRs.

Need help? Contact support

Can a PCR be signed electronically?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA provisions, electronic signatures are generally valid for contracts and amendments unless a specific exception applies.
When is notarization required?
Notarization is seldom required for ordinary contract amendments, but it may be necessary when the change conveys real property or a statute or contract specifically requires an acknowledgement.
Who can sign a PCR for a company?
A PCR must be executed by a person authorized under the contract or corporate authority. If authority is unclear, attach a corporate resolution or POA showing delegated signing rights.
How should you store executed PCRs?
Store signed PCRs in a secure document repository as PDF/A or equivalent, preserve the audit trail, and retain per applicable retention rules (see IRS, HIPAA, and state requirements).
What if an approver refuses to sign?
Document the refusal and reason, escalate per the contract’s dispute or change governance clauses, and avoid implementing the change until approved to prevent breach claims.
Are click-to-sign approvals legally sufficient?
Click-to-sign can be sufficient if it demonstrates signer intent, consent to electronic transactions, attribution, and retention capability consistent with ESIGN/UETA requirements.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now