Can this Extension be signed electronically?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the parties consent and the electronic record is retained and reproducible.

Do parties ever need a notary or witness?

Most contract amendments do not require notarization, but specific state rules or related document types (deeds, powers of attorney) may. Verify local notary or witness requirements before execution.

What happens if an unauthorized person signs?

A signature by an unauthorized person risks non-enforceability; corrective measures include ratification by an authorized signatory or re-execution under proper authority.

How do I correct a signed extension?

If an executed Extension contains an error, prepare a corrective amendment or rescission and re-execute with the same formalities as the original amendment to ensure a clean audit trail.

Are audit trails required for enforceability?

Audit trails are not strictly required by ESIGN/UETA, but they provide essential evidence of intent, attribution, and the signing event, improving enforceability in practice.

How long until the amendment takes effect?

The effective date is controlled by the Extension text. If not specified, courts will look to intent and performance; specifying an explicit MM/DD/YYYY date avoids uncertainty.

Electronic Signature
Templates
Project Management
Project Management Partnering Extension

Project Management Partnering Extension

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

Project Management Partnering Extension

Project Identification

Project Title Project ID Client Name Service Provider Project Manager (Provider) Original Partnering Agreement Effective Date

Recitals

This Partnering Extension ("Extension") is entered into by Client Name: and Service Provider: to modify certain terms of the Partnering Agreement identified above. The parties desire to extend the term, adjust deliverables and adjust budgetary provisions as set forth in this Extension.

Extension Term

The term of the Partnering Agreement is hereby extended to a new Contract End Date: , unless earlier terminated in accordance with the Agreement. All obligations and rights of the parties during the extended term shall remain in force except as expressly modified herein.

Scope of Work

Revised Scope of Work (Describe additions or modifications) Out-of-Scope Items (explicitly retained as out-of-scope)

Deliverables and Acceptance

Deliverable 1: — Due:

Acceptance Criteria for Deliverable 1

Deliverable 2: — Due:

Acceptance Criteria for Deliverable 2

Timeline & Milestones

Contract Start Date Contract End Date Key Milestones

Budget & Payment

Total Additional Compensation (if any) Revised Payment Schedule Change Order Authorization Required

Check to require written and signed change orders for any scope or budget adjustments beyond those set forth in this Extension.

Change Order Process

Confidentiality

Except as expressly modified herein, the nondisclosure, confidentiality and data protection provisions of the Partnering Agreement remain in full force and effect. Each party shall continue to protect Confidential Information of the other party using at least the same degree of care it uses to protect its own confidential information, but no less than a reasonable standard of care.

Representations, Warranties & Liability

Each party represents and warrants that it has the authority to enter into this Extension and to perform its obligations hereunder. Except as expressly modified herein, all limitations of liability, indemnification obligations and warranty disclaimers set forth in the Partnering Agreement shall remain applicable, subject to any adjustments expressly set forth in this Extension.

Termination

Termination rights under the Partnering Agreement shall continue to apply during the extended term. Notwithstanding the foregoing, either party may terminate this Extension for material breach of the modifications set forth herein if the breaching party fails to cure within the time provided in the Agreement.

Notices

Client Notice Address Provider Notice Address

Governing Law & Dispute Resolution

This Extension shall be governed by and construed in accordance with the laws of the state or jurisdiction identified below, without regard to conflict of laws principles. The parties agree that any dispute arising out of or relating to this Extension shall be resolved pursuant to the dispute resolution provisions of the Partnering Agreement, unless otherwise specified here: Governing Jurisdiction:

Integration

Except as expressly set forth in this Extension, all terms and conditions of the Partnering Agreement remain unchanged and in full force and effect. This Extension, together with the Partnering Agreement and any prior written amendments specifically referenced herein, constitutes the entire agreement between the parties with respect to the subject matter hereof.

Authority

Each signatory below represents and warrants that they are duly authorized to execute this Extension on behalf of the party for whom they sign and that this Extension is binding upon such party in accordance with its terms.

Client:

By:

Date:

Service Provider:

By:

Date:

What the Project Management Partnering Extension Is

The Project Management Partnering Extension is a supplemental agreement used to adjust or extend the scope, schedule, responsibilities, or contracting terms on an existing project management or construction partnering agreement. It documents agreed changes to timelines, milestones, resource allocation, payment schedules, dispute-resolution steps, and any new deliverables. The Extension becomes part of the master agreement when signed by authorized representatives and should reference the original contract, the effective date of the change, and the specific sections being amended to avoid ambiguity in enforcement and performance obligations.

Why a Partnering Extension Matters for Project Controls

A Partnering Extension preserves a clear, auditable record of mutual changes to project scope, responsibilities, and schedule so parties avoid disputes and align expectations. It reduces risk by documenting consideration, the effective date, and any adjusted dispute-resolution or payment mechanics in one concise amendment.

Who Typically Prepares and Signs This Extension

Use this extension when parties want a simple, enforceable amendment that ties directly back to the controlling contract and records who approved each change.

Prime contractor representatives who approve scope and schedule changes within delegated authority.
Subcontractors or specialty trades when their scope or delivery dates shift and written consent is required.
Owner or client contract administrators who must accept budget, milestone, or deliverable adjustments.

Typical Signatories and Their Roles

Project Manager

Project managers initiate the Extension request, summarize technical changes, and coordinate internal approvals; they are not always authorized to bind financial commitments without additional signatory approval from finance or contracting.

Authorized Signatory

An authorized signatory (company officer or delegated representative) executes the Extension to create binding obligations; confirm delegated signature authority prior to execution to prevent enforcement challenges.

Key Required Data Elements

Reference: Original contract number

Effective Date: MM/DD/YYYY

Parties: Full legal names

Scope Change: Short description

Consideration: Amount or statement

Signature Block: Name / Title / Date

Step-by-Step: Completing the Partnering Extension

Follow these steps to prepare, review, and execute the extension so changes are clearly documented and enforceable.

01

Draft: Identify contract sections to amend and describe changes succinctly.
02

Review: Legal and project teams check scope, budget, and risk allocation.
03

Approve: Obtain internal approvals per delegated authority matrix.
04

Execute: All authorized parties sign and date the Extension.

How to Configure an Online Workflow for This Extension

Set up a digital workflow to route the Extension for review, approval, and e-signature with clear signer order and authentication requirements.

Field	Configuration
Signer Order	Define sequence (Owner → Prime → Subcontractor)
Authentication	Email link or SMS code; use stronger KBA if required
Required Fields	Make Effective Date, Consideration, and Signatures mandatory
Retention	Enable audit trail and store final PDF in contract repository

Where the Completed Extension Goes and Who Receives It

After execution, route copies to internal stakeholders and the contract repository to maintain a single authoritative amendment record.

Owner Copy: Delivered to owner for file and accounting
Contractor Copy: Retained by prime contractor in project folder
Subcontractor Copy: Sent to affected subcontractors
Records: Stored in document management system

Digital Signing and Submission Considerations

Ensure the chosen process meets ESIGN/UETA requirements and any industry-specific rules before relying solely on electronic execution.

Authentication: Email + SMS code or higher assurance
Format Support: PDF and DOCX export required
Integrations: Connect to contract repository or ERP

Typical Timing and Deadlines for Extensions

Be aware of internal approval SLAs and any statutory deadlines that might affect the Extension's effective date or payment timing.

Request Lead Time:

Submit change request at least 7–14 days before milestone changes

Internal Approval SLA:

Typical 3–10 business days for legal and finance review

Effective Date:

Use clear MM/DD/YYYY effective dates to avoid ambiguity

Payment Adjustment:

State payment terms and new invoicing schedule

Record Retention:

File executed copy within 5 business days

Common Preparation Errors to Avoid

Failing to reference the original contract section allows competing interpretations and increases dispute risk.
Using vague consideration language such as 'additional compensation' without amounts or calculation method creates enforcement gaps.
Missing delegated authority checks can render a signature non-binding and require re-execution under delay.
Not updating related schedules, exhibits, or milestone logs leads to inconsistent project controls and invoicing errors.

Consequences of Incorrect or Unexecuted Extensions

Contract Ambiguity: Increased dispute likelihood

Invalid Signature: Possible non-enforceability

Late Payment Penalty: Damages or interest

Regulatory Risk: Compliance exposure

I-9 Penalty: $281–$2,789 possible for I-9 violations

Tax Penalty: $60–$660+ per form (IRC §6721)

Real-World Examples of Using an Extension

Here are two real customer examples illustrating how parties used partnering extensions to document project changes and keep work moving.

Optica Ventures — Change Execution

The team needed a quick amendment to add a two-week schedule extension due to permit delays.

The Extension specified new milestone dates and payment holdbacks.
By documenting the change and routing for e-signature, both parties avoided a formal dispute and updated project controls promptly.

Martin Properties — Remote Signing

A property manager required multiple vendor approvals for a scope expansion mid-project.

The Extension combined scope detail, updated budget, and signatures from remote vendors.
Using an auditable electronic workflow, all parties signed without in-person meetings and the project resumed on the new timeline.

Practical Tips for Accurate, Efficient Completion

Apply these practices to reduce rework, accelerate approvals, and create a defensible amendment record.

Reference Precisely

Cite the specific original contract sections, exhibit numbers, and clause names being amended so reviewers can quickly verify intent and scope. Ambiguity leads to disputes and slows approvals.

Use Clear Consideration Language

Specify exact dollar amounts, formulas, or caps for additional compensation, including payment timing and invoicing procedures, to prevent later payment disputes or withholding.

Confirm Signature Authority

Verify that signers are authorized to bind their organization and note any required corporate approvals; consider attaching a delegation of authority if signatures are outside normal limits.

Maintain an Audit Trail

Use a system that captures timestamps, signer authentication, IP addresses, and a PDF certificate of completion to support enforceability and post-execution audits.

eSignature Vendor Pricing Comparison for Executing Extensions

Per-user pricing and core features influence platform selection; signNow is listed first with publicly published plan starting points and feature notes for quick reference.

	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	Verify with vendor	Verify with vendor	Verify with vendor	Verify with vendor
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions About Partnering Extensions

Answers to common execution and enforceability questions when preparing or signing a Project Management Partnering Extension.

Need help? Contact support

Can this Extension be signed electronically?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the parties consent and the electronic record is retained and reproducible.
Do parties ever need a notary or witness?
Most contract amendments do not require notarization, but specific state rules or related document types (deeds, powers of attorney) may. Verify local notary or witness requirements before execution.
What happens if an unauthorized person signs?
A signature by an unauthorized person risks non-enforceability; corrective measures include ratification by an authorized signatory or re-execution under proper authority.
How do I correct a signed extension?
If an executed Extension contains an error, prepare a corrective amendment or rescission and re-execute with the same formalities as the original amendment to ensure a clean audit trail.
Are audit trails required for enforceability?
Audit trails are not strictly required by ESIGN/UETA, but they provide essential evidence of intent, attribution, and the signing event, improving enforceability in practice.
How long until the amendment takes effect?
The effective date is controlled by the Extension text. If not specified, courts will look to intent and performance; specifying an explicit MM/DD/YYYY date avoids uncertainty.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now