Establishing secure connection…Loading editor…Preparing document…

Project Management SUPP1 Template

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

PROJECT MANAGEMENT SUPP1 TEMPLATE

Project Identification

Scope of Work

The Service Provider will perform the work described below in accordance with the terms of this SUPP1. The work shall be performed in a professional manner consistent with industry standards.

Deliverables and Acceptance

Each deliverable shall be accompanied by acceptance criteria. Acceptance shall be deemed granted when the Client issues written acceptance or when no rejection is received within the acceptance period specified below.

Planned delivery date:

Planned delivery date:

Timeline & Milestones

The timeline below establishes target dates. Time is of the essence only where specifically indicated in the schedule.

Milestone 1 Date:

Milestone 2 Date:

Budget & Payment

Payment Type:

Confidentiality

Each party acknowledges that it may receive Confidential Information from the other. Confidential Information includes non-public business information, technical data, deliverables, trade secrets, and any information marked or reasonably understood to be confidential. The receiving party shall: (a) use Confidential Information only to perform its obligations under this SUPP1; (b) restrict disclosure to employees, subcontractors or advisors who have a need to know and are bound by confidentiality obligations; and (c) take commercially reasonable measures to protect such information.

Confidentiality Period (from effective date):

Warranties, Indemnification & Insurance

The Service Provider warrants that the deliverables will materially conform to the accepted deliverable specifications for a period specified below. Except as expressly stated, all other warranties are disclaimed to the fullest extent permitted by law.

Indemnification: The Service Provider agrees to indemnify, defend and hold harmless the Client from third-party claims arising out of gross negligence, willful misconduct, or material breach of this SUPP1 by the Service Provider, subject to the limitations of liability set forth below.

Termination

Either party may terminate this SUPP1 for material breach if the breach remains uncured for the notice period below following written notice. Upon termination, the Client shall pay the Service Provider for all work performed and approved expenses up to the effective date of termination, subject to setoffs for breach.

Limitation of Liability; Governing Law

Except to the extent prohibited by applicable law, the aggregate liability of either party arising out of or related to this SUPP1 shall not exceed the total amounts paid to the Service Provider under this SUPP1 during the twelve (12) month period preceding the claim. Neither party shall be liable for incidental, consequential, or punitive damages except for liability arising from gross negligence or willful misconduct.

Acceptance Procedure

Upon delivery, the Client shall have the stated acceptance period to review and either accept or provide a written list of deficiencies. If no written deficiencies are provided within the acceptance period, the deliverable shall be deemed accepted.

Administrative Provisions

Notices required under this SUPP1 shall be in writing and delivered to the contact details provided above. This SUPP1, together with any referenced statements of work or master agreement, constitutes the entire agreement between the parties with respect to the subject matter herein and supersedes prior negotiations and representations.

Client Name:

By:

Date:

Service Provider Name:

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What the Project Management SUPP1 Template Is

The Project Management SUPP1 Template is a supplemental project document used to record scope adjustments, task-level clarifications, and administrative details that attach to a primary project agreement. It captures change descriptions, affected deliverables, revised schedules, responsible parties, cost impacts, and approval signatures. Organizations use SUPP1 to maintain an auditable record of incremental project decisions without reissuing the main contract. The template is designed for reuse across projects and can be completed as a standalone amendment, appended exhibit, or integrated into electronic workflows for routing, signature, and archival.

Why a Standard SUPP1 Template Matters

A standardized Project Management SUPP1 Template reduces ambiguity by requiring consistent fields for scope, schedule, cost, and approvals, supporting traceability across project phases and simplifying audits and handoffs.

Why a Standard SUPP1 Template Matters

Who Typically Completes a SUPP1

Teams that prepare or approve SUPP1 entries include project managers, contract administrators, commercial leads, and delegated approvers from client or vendor organizations.

  • Project Manager — Prepares scope changes, updates schedule impacts, and routes for approval within the project team.
  • Contract Administrator — Verifies contractual compliance, updates reference to the master agreement, and logs cost effects.
  • Client Representative — Reviews impacts on acceptance criteria, signs approvals, and confirms funding or change order authorization.

Use SUPP1 when a discrete change or clarification needs a written amendment that preserves the original agreement while documenting the modification.

Essential Parts of a Professional SUPP1

A complete SUPP1 includes administrative headers, a clear description of the change, impact analysis, cost and schedule adjustments, approver blocks, and a version control section to track edits.

Header

Project identifiers, SUPP1 number, effective date, and reference to the original contract or purchase order to ensure a clear linkage.

Change Summary

Concise description of the modification, the reason for the change, and the specific sections or deliverables affected within the baseline scope.

Scope Details

Detailed line-item changes to tasks, acceptance criteria, or deliverables including measurable outputs, quantities, and technical descriptions where applicable.

Schedule Impact

Revised milestone dates, float impacts, critical path adjustments, and any interim deliverables or phased acceptance dates.

Cost and Funding

Itemized cost changes, funding source, change order total, payment terms, and any budget reallocation or contingency utilization.

Approvals

Designated signatory lines for project manager, commercial lead, client approver, plus date and signature fields for clear authorization.

Required Data Elements at a Glance

Project ID: Unique contract identifier
SUPP1 Number: Sequential amendment number
Effective Date: MM/DD/YYYY format
Affected Deliverable: Name or milestone code
Cost Change: Dollar amount or zero
Approver: Name and role

Step-by-Step: Filling Out SUPP1

Follow these steps to complete a single SUPP1 record accurately and to create a clear audit trail for approvals and downstream processing.

  • 01
    Identify: Record project ID and reference agreement.
  • 02
    Describe: Summarize the change in plain language.
  • 03
    Quantify: Enter schedule and cost impacts.
  • 04
    Approve: Collect signatures and dates.

How to Configure an Online SUPP1 Workflow

Typical workflow settings support routing, conditional approvals, and automated notifications to ensure timely review and signature capture.

Field Configuration
Route Order Sequential or parallel signer order
Authentication Email link or SMS code
Conditional Fields Show cost fields only if cost change indicated
Retention Auto-archive signed PDF to records system

Where SUPP1 Goes Once Completed

A completed SUPP1 typically moves through approval, archival, and integration stages; map these to existing contract management processes.

  • Routing: Send to approvers in defined order via email or signing link.
  • Execution: Capture signatures and certificate of completion.
  • Integration: Attach signed SUPP1 to the master contract record.
  • Archive: Store final PDF in document management system.

Delivering and Sharing SUPP1 Electronically

Digital distribution choices affect signer experience, auditability, and storage — choose platforms that support required authentication and retention.

  • Email Link: Simple delivery, email authentication
  • Secure Portal: Higher control, user accounts required
  • API Integration: Automated transfer to ERP or CMS

Select a method that aligns with legal requirements, internal policy, and the signers' access; ensure the platform captures an audit trail and produces a tamper-evident final file for records.

Typical Timelines and Processing Expectations

Set clear internal deadlines to avoid project drift; align SUPP1 turnaround expectations with procurement and billing cycles.

Internal Review Window:

2–5 business days for initial review

Approver Response Time:

5–10 business days recommended

Execution Deadline:

Tie to effective date or milestone change

Archival:

Archive signed SUPP1 within 48–72 hours

Invoice Alignment:

Coordinate with next billing run to reflect cost changes

Common Errors to Avoid When Preparing SUPP1

  • Leaving the master agreement reference blank, which prevents auditors from linking the amendment to the parent contract and can cause acceptance disputes.
  • Failing to quantify schedule impacts precisely, such as omitting revised milestone dates or critical path changes that affect deliverable acceptance.
  • Using vague cost language like 'additional fees apply' instead of stating a specific dollar amount or formula for calculating charges.
  • Collecting initials instead of full signatures when the template requires executed approvals, creating ambiguity about authorization validity.

Risks and Consequences of an Incorrect SUPP1

Contract Dispute: Ambiguous changes invite interpretation disputes
Payment Delay: Missing cost approvals pause invoicing
Schedule Slippage: Unrecorded critical path shifts cause delays
Audit Findings: Incomplete records trigger compliance exceptions
Legal Exposure: Unsigned amendments may be unenforceable
Rework Costs: Correcting errors consumes time and money

eSignature Vendor Snapshot for SUPP1 Workflows

Comparison of common eSignature vendor attributes for executing and managing SUPP1 documents; signNow is listed first per vendor order.

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 Yes, 7-day 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

How Teams Use SUPP1 in Practice

Real-world examples show how SUPP1 records reduce confusion and speed approvals across projects.

Large Construction Project

A contractor documents a scope increase for an electrical package

  • change included revised completion dates and additional subcontractor coordination
  • the SUPP1 was used to update the payment schedule, attach a revised Gantt extract, and obtain client sign-off to avoid claim delays.

Software Rollout

An IT vendor logs a minor feature addition requested after sprint planning

  • the change described required minimal cost but shifted delivery of a dependent module by two weeks
  • SUPP1 captured the acceptance criteria change and routed approvals through product, legal, and finance to enable timely invoicing.

How to Amend an Existing SUPP1

Use this grid when a previously issued SUPP1 needs revision; track version history to avoid conflicting amendments.

01

Identify Amendment:

Locate original SUPP1 number
02

Prepare Revision:

Mark redline or summary
03

Notify Parties:

Inform all original approvers
04

Re-approve:

Collect fresh signatures
05

Archive:

Store revised SUPP1 with version notes
06

Communicate:

Distribute final to stakeholders

Who May Legally Sign a SUPP1

Authorized Signatory

The person who signs must have delegated authority under the master agreement or corporate resolution. Confirm signing authority in procurement or vendor master records before execution to avoid disputes about enforceability.

Project Approver

Often a project manager or commercial lead is authorized for operational changes under a specified monetary threshold. Larger cost changes typically require higher-level commercial or executive sign-off per internal authority matrices.

Notarization and Witness Steps When Required

If SUPP1 modifies real-property rights or otherwise requires notarization, follow an ordered authentication flow to preserve validity.

01

Prepare Document

Ensure notarization block and witness lines are present

02

Identity Check

Signer presents ID to notary

03

Witnesses Join

Witnesses sign where required

04

Notary Acknowledges

Notary signs and stamps the acknowledgement

05

Record Retention

Keep notarized copy with contract file

06

RON Option

Use Remote Online Notarization if state law permits

07

Journal Entry

Notary records session details

08

Distribute

Send final notarized PDF to stakeholders

Frequently Asked Questions About SUPP1

Practical answers to common execution, signing, and storage questions for SUPP1 templates when used in U.S. projects.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.