Can this supplement be signed electronically?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the parties demonstrate intent, consent, attribution, and a reproducible record.

When is notarization necessary?

Notarization is not typically required for commercial supplementary agreements unless state law or a specific contract clause requires an acknowledged signature for recordation or evidentiary purposes.

What happens if a name mismatch occurs?

A signer name mismatch can cause attribution issues. Use the signer's exact legal name; correct mismatches promptly and obtain re-execution or an attestation to preserve enforceability.

How should confidential information be handled?

Include a confidentiality clause or reference the master NDA. Limit disclosed data, specify permitted recipients, and note retention and destruction obligations.

Are healthcare projects different?

Yes. If the supplement involves PHI, include a Business Associate Agreement and follow HIPAA safeguards; obtain a BAA before exchanging protected health information.

Which signer authentication is recommended?

Use at least email verification plus optional SMS or identity proofing for higher-risk agreements. Stronger authentication reduces fraud risk and strengthens attribution evidence.

Electronic Signature
Templates
Project Management
Project Management Supplementary Agreement

Project Management Supplementary Agreement

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

PROJECT MANAGEMENT SUPPLEMENTARY AGREEMENT

Project Identification

Project Title Project ID Client Name Service Provider Project Manager (Service Provider)

Effective Date:

Recitals

This Supplementary Agreement is entered into between Client Name: and Service Provider: to amend and supplement the original Project Agreement dated titled .

The parties agree that the terms of this Supplementary Agreement shall prevail to the extent of any conflict with the original agreement. All capitalized terms used but not defined herein shall have the meanings assigned in the original agreement.

Scope of Work (Supplement)

Expanded Scope of Work Out-of-Scope Items

Deliverables and Acceptance Criteria

Deliverable 1 — Title:

Deliverable 1 Description Acceptance Criteria

Due Date:

Deliverable 2 — Title:

Deliverable 2 Description Acceptance Criteria

Due Date:

Timeline and Milestones

Project Start Date Projected End Date Milestones (Name and Date)

Budget and Payment

Total Supplement Amount (USD) Payment Schedule Change Order Process

Standard change order markup rate (if applicable):

Confidentiality

The parties acknowledge that, in the performance of the supplemental scope, each party may receive Confidential Information of the other. Confidential Information shall be held in confidence for a period of years from the date of disclosure and shall only be used for purposes of performance under this Supplementary Agreement. Disclosure is permitted where required by law, provided the disclosing party is given prompt notice to seek protective measures.

Liability, Indemnity, and Insurance

Each party agrees to indemnify and hold harmless the other from claims arising out of its negligent acts or willful misconduct in performance of the supplemental work. Except for indemnity obligations and breaches of confidentiality, the parties' aggregate liability for claims arising from this Supplementary Agreement shall be limited to the total fees paid under this Supplement during the twelve (12) months preceding the claim.

Termination

Either party may terminate this Supplementary Agreement for material breach if the breaching party fails to cure within days following written notice. Upon termination for any reason, the Service Provider shall be entitled to payment for work performed and accepted through the effective date of termination.

Amendments and Notices

This Supplementary Agreement may be amended only by a written instrument executed by authorized representatives of both parties. Notices required under this Supplement shall be delivered to the contact persons set forth below.

Client Contact for Notices Service Provider Contact for Notices

Governing Law and Dispute Resolution

This Supplementary Agreement shall be governed by the laws of: . The parties agree to negotiate in good faith to resolve disputes and, if unresolved, to submit the dispute to the dispute resolution mechanism agreed in the original agreement.

Entire Agreement

Except as expressly amended by this Supplementary Agreement, all terms of the original agreement remain in full force and effect. This Supplement, together with the original agreement, constitutes the entire agreement between the parties with respect to the subject matter herein.

Client — Printed Name:

By:

Date:

Service Provider — Printed Name:

By:

Date:

What the Project Management Supplementary Agreement Is

A Project Management Supplementary Agreement is a contract amendment or companion document that defines project-specific obligations, deliverables, schedules, change-order procedures, and payment triggers that supplement a primary services or prime contracting agreement. It clarifies roles, acceptance criteria, reporting and dispute-resolution processes for a defined project scope, and may attach technical exhibits or schedules. Parties use it to limit ambiguity about responsibilities during execution, link payments to milestones, and document agreed changes without rewriting the underlying master agreement.

Why adding a supplementary agreement improves project clarity

A focused supplementary agreement isolates project terms (scope, milestones, payment schedule, acceptance criteria) from broader master contracts, reducing ambiguity and disputes. It lets stakeholders approve project-specific changes, record negotiated variations, and align legal and operational teams on delivery metrics without altering the core contract.

Who typically prepares and signs this agreement

Several roles are commonly involved in creating and executing a Project Management Supplementary Agreement; each has distinct responsibilities during drafting and approval.

Project Managers responsible for day-to-day delivery and milestone sign-off, ensuring technical exhibits and schedules match operational plans.
Procurement or Contracts Teams who review legal terms, payment triggers, and change-order authority to protect organizational interests.
Finance or Accounts Payable staff who confirm milestone definitions align with invoicing and payment schedules to avoid payment disputes.

Coordinating these roles early shortens negotiation cycles and reduces rework when the agreement is routed for signatures and approvals.

Primary signers and their responsibilities

Project Manager

The Project Manager approves scope changes, confirms milestone completion, and provides technical acceptance. Their signature ties operational acceptance to contractual payment events and ensures deliverables meet documented standards.

Authorized Signatory

An authorized executive or contracting officer signs for legal acceptance and payment authority. This signer must have corporate authority and is responsible for binding the organization to amended terms.

Essential compliance and security markers to include

Encryption: AES-256 at rest

Transport Security: TLS 1.2/1.3

Audit Trail: Timestamps and IP logs

Regulatory Fit: ESIGN / UETA

Healthcare: HIPAA (BAA required)

Quality: SOC 2 Type II

Common pitfalls to avoid when preparing the agreement

Vague scope language that omits measurable acceptance criteria, creating disputes over whether deliverables meet requirements.
Missing effective date or inconsistent dates between the supplementary agreement and attachments, which can create gaps in enforcement.
Undefined change-order process that leaves authorization and cost responsibilities unclear when scope shifts mid-project.
Failure to align milestone definitions with invoicing procedures, leading to delayed payments and strained supplier relationships.

Core elements every professional supplementary agreement should include

Include concise, measurable components that map directly to delivery and payment processes so both operational and legal teams can verify compliance and performance.

Parties

Full legal names and entity types for each party, including any parent company details and a designated contract contact for notices and escalation.

Scope of Work

A precise description of tasks, deliverables, technical specifications, and exclusions. Attach exhibits or SOW appendices where necessary to avoid ambiguity.

Milestones & Deliverables

Clearly defined milestones, deliverables, and acceptance criteria with dates or event triggers that map to payment obligations and reporting cadence.

Payment Terms

Payment schedule tied to milestone acceptance, invoicing requirements, allowable expenses, and any retainage or holdback provisions.

Change Orders

A documented approval workflow for scope changes, pricing adjustments, and schedule impacts, including who can authorize and how cost impacts are calculated.

Dispute & Termination

Procedures for dispute resolution, notice requirements, termination rights, cure periods, and post-termination obligations such as deliverable transfer.

Step-by-step: completing a Project Management Supplementary Agreement

Follow these sequential steps to draft, review, and finalize the supplementary agreement so signatures and payments occur without administrative delay.

01

Draft: Populate parties, scope, milestones, and payment terms clearly.
02

Internal Review: Contracts, finance, and project leads verify technical and commercial alignment.
03

External Review: Share with counterparty for redlines and confirm change-order process.
04

Execute: Obtain authorized signatures and record the signed agreement for retention.

Configuring a digital workflow for this agreement

Set up an electronic workflow that enforces field completion, signer order, and retention to accelerate approvals and maintain an auditable trail.

Field	Configuration
Authentication	Use email plus optional SMS code for signer attribution.
Bulk Send	Enable for mass distribution of standardized supplements.
Conditional Fields	Show or hide sections based on role or answer selections.
Audit Trail	Capture timestamps, IP addresses, and action logs for each signer.

Technical considerations for electronic completion

Choose a platform that supports required authentication, field validation, and compliant retention for the document's industry and jurisdiction.

File Formats: PDF, DOCX supported
Integrations: Salesforce, NetSuite, Microsoft 365
Authentication: Email, SMS, KBA

Typical electronic signing flow for the agreement

A consistent electronic flow reduces signer friction and ensures each step generates verifiable evidence of consent and completion.

Upload Document: Place signature and data fields in the template.
Assign Signers: Set signer order and authentication method.
Send for Signature: Signers receive secure link or email invite.
Store & Audit: Signed copy and audit trail stored in repository.

Key dates to verify before execution

Confirm these dates to avoid disputes over performance, invoicing, and limitation periods before routing the agreement for signature.

Effective Date:

Date obligations begin; use MM/DD/YYYY format.

Sign-By Date:

Deadline for executing the supplement to secure milestone timing.

Milestone Deadlines:

Specific dates tied to payment and acceptance.

Notice Periods:

Time required for change-order or termination notices.

Record Retention:

Retention start date for compliance tracking.

Consequences of incomplete or incorrect supplementary agreements

Contract Unenforceable: Risk of invalid terms

Payment Delays: Invoices may be withheld

Tax Exposure: Incorrect reporting consequences

Regulatory Risk: HIPAA/Federal noncompliance

Dispute Costs: Increased legal fees

Reputational Harm: Client relationship damage

eSignature vendor comparison for executing supplementary agreements

A concise feature and pricing snapshot across common eSignature vendors to inform platform selection for secure, auditable execution.

	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	Varies	Varies	Varies
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	Varies	Varies

Real-world examples of supplementary agreement use

These illustrative cases show how organizations use a Project Management Supplementary Agreement to resolve scope, schedule, and payment coordination.

Optica Ventures LLC

Optica attached a detailed milestone schedule to a master services agreement to remove ambiguity on deliverables.

The supplement defined three acceptance tests tied to payments.
Brian Fitzgibbons, COO, noted that a clear supplementary agreement helped reduce review cycles and aligned vendor deliverables with client expectations.

Martin Properties

A property renovation project used a supplementary agreement to document phased payments and inspection triggers.

The supplement included holdback and completion definition language.
Tim Martin, Founder, reported improved compliance and a single point-of-record for milestone approvals facilitating faster invoice processing.

Frequently asked questions about completing and executing the agreement

Answers to common legal, technical, and process questions about Project Management Supplementary Agreements and electronic execution.

Need help? Contact support

Can this supplement be signed electronically?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the parties demonstrate intent, consent, attribution, and a reproducible record.
When is notarization necessary?
Notarization is not typically required for commercial supplementary agreements unless state law or a specific contract clause requires an acknowledged signature for recordation or evidentiary purposes.
What happens if a name mismatch occurs?
A signer name mismatch can cause attribution issues. Use the signer's exact legal name; correct mismatches promptly and obtain re-execution or an attestation to preserve enforceability.
How should confidential information be handled?
Include a confidentiality clause or reference the master NDA. Limit disclosed data, specify permitted recipients, and note retention and destruction obligations.
Are healthcare projects different?
Yes. If the supplement involves PHI, include a Business Associate Agreement and follow HIPAA safeguards; obtain a BAA before exchanging protected health information.
Which signer authentication is recommended?
Use at least email verification plus optional SMS or identity proofing for higher-risk agreements. Stronger authentication reduces fraud risk and strengthens attribution evidence.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now