Establishing secure connection…Loading editor…Preparing document…

Project Management SUP1 Template

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

PROJECT MANAGEMENT SUP1 TEMPLATE

Project Identification

Project Title:

Project ID:    Effective Date:

Scope of Work

The Service Provider shall perform the services and deliver the deliverables described below in accordance with the terms and conditions of this SUP1 Template. Services shall be performed with reasonable skill, care and diligence in accordance with industry standards.

Deliverables & Acceptance

Each listed deliverable must include acceptance criteria. Client acceptance is required in writing and will be provided within the acceptance period specified below, subject to the acceptance tests described.

Due Date:

Due Date:

Due Date:

Timeline & Milestones

Project Start Date:    Project End Date:

Milestone 1 Date:

Milestone 2 Date:

Budget & Payment

Total Contract Value (USD):

Acceptance Testing & Warranty

Client shall have a period of 10 business days following delivery of each deliverable to perform acceptance testing in accordance with the acceptance criteria. If the deliverable fails acceptance testing, Service Provider shall remediate defects at no additional cost until criteria are met. Warranties provided shall be limited to remedies set forth herein unless otherwise agreed in writing.

Confidentiality

Each party agrees to treat as confidential all non-public information received in connection with the performance of this Agreement and to use such information only for the purposes of performing obligations hereunder. Confidential information does not include information that is lawfully in the receiving party's possession without confidentiality obligations, is or becomes publicly available through no breach, or is independently developed.

Intellectual Property

Unless otherwise agreed in writing, Service Provider grants Client a perpetual, non-exclusive license to use deliverables for Client's internal business purposes upon full payment. Service Provider retains ownership of pre-existing tools, methodologies and background IP. Any transfer of ownership must be stated expressly and signed by both parties.

Liability & Indemnification

Except for liability arising from willful misconduct or gross negligence, each party's aggregate liability under this Agreement shall be limited to the total fees paid to Service Provider under this SUP1 Template. Each party shall indemnify the other from third-party claims arising from that party's breach of representations, warranties or willful misconduct.

Termination

Either party may terminate for material breach if the breaching party fails to cure within 30 days after written notice. On termination, Client shall pay Service Provider for all work performed through the effective date of termination and for any non-cancellable commitments reasonably incurred.

Governing Law & Dispute Resolution

This SUP1 Template shall be governed by the laws of the jurisdiction identified below. Parties shall attempt in good faith to resolve disputes by negotiation prior to pursuing formal remedies.

Notices

All notices required or permitted under this SUP1 Template shall be in writing and delivered to the addresses set forth below or to such other address as a party designates by notice.

Additional Provisions

Entire Agreement: This SUP1 Template, together with any referenced exhibits or attachments executed by the parties, constitutes the entire agreement and supersedes prior agreements relating to the same subject matter. Any amendment must be in writing and signed by authorized representatives of both parties.

Client

Client Name (Print):

By:

Date:

Service Provider

Service Provider Name (Print):

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 SUP1 Template Is and where it fits

Project Management SUP1 Template is a standardized supplemental project document used to record scope clarifications, deliverable schedules, change orders, and approvals during a project's lifecycle. Typically attached to a primary contract or work order, it formalizes responsibilities, milestones, payment triggers, and acceptance criteria so stakeholders share a single authoritative reference. The template supports versioning and signatory blocks for parties and vendors, and is designed for both paper and electronic workflows. Using a consistent SUP1 template reduces ambiguity, creates an auditable record of changes, and helps align expectations across project teams, contractors, and clients.

Why standardizing SUP1 matters for project execution

Using the Project Management SUP1 Template standardizes change documentation, clarifies scope and acceptance criteria, and preserves an auditable record of approvals and decisions. Consistent use reduces disputes, accelerates approvals, and supports compliance with contract administration processes.

Why standardizing SUP1 matters for project execution

Who typically prepares and relies on a SUP1

Project managers, contract administrators, construction managers, and procurement teams frequently complete the Project Management SUP1 Template during project execution and change control.

  • Project managers overseeing delivery, change orders, approvals, and status reporting across multiple phases.
  • Contract administrators managing contractual amendments, milestone adjustments, and payment triggers tied to contract terms.
  • Vendors and subcontractors providing deliverable acceptance, cost confirmations, and formal sign-off on scope changes.

The template also serves legal, audit, and finance teams that verify approvals and reconcile billing against approved changes.

Essential parts of a professional SUP1 document

Core elements of a professional Project Management SUP1 Template ensure traceable changes, clear responsibilities, and measurable acceptance criteria for each deliverable and milestone.

Header

Project and contract identifiers, revision number, effective date, parties, and contact information. Use consistent naming conventions to avoid version confusion and link the SUP1 to the primary contract.

Scope

Concise description of changed or supplemental work, boundaries, exclusions, and acceptance criteria. Tie scope changes to specific contract clauses to ensure enforceability and clarity for delivery teams.

Schedule

Revised milestone dates, delivery windows, and dependencies. Include responsible party and resource assumptions so timeline changes are actionable and integrated into the master schedule.

Payments

Payment terms tied to deliverables or milestones, including amounts, invoicing instructions, and acceptance-based payment triggers to prevent billing disputes and automate approvals.

Approvals

Signatory blocks with printed names, titles, signature, and date fields for all approving parties. Include witness or notary lines if required by jurisdiction or contract.

Audit Trail

Version history, change log, references to associated documents, and space for notes. Maintain timestamps and signer identifiers to support audits and dispute resolution.

Step-by-step: complete and execute a SUP1

Follow these steps to complete and execute a SUP1, ensuring consistent approval and auditability across project stakeholders.

  • 01
    Prepare Draft: Populate fields, attach exhibits, and verify identifiers.
  • 02
    Review Internally: Circulate to PMO and legal for comments.
  • 03
    Obtain Signatures: Collect approvals via e-signature or wet-signature.
  • 04
    Distribute Copies: Send final PDF and record audit trail.

Typical online workflow settings for SUP1 processing

Configure online workflow settings to automate routing, authentication, and storage of SUP1 documents for consistent processing.

Workflow field and configuration mapping Field name | Recommended configuration and options
Routing order and signer sequence Sequential routing; set signer order and escalation rules.
Authentication method, verification, and strength Email link by default; use SMS or KBA for higher assurance.
Document retention and version control Archive signed SUP1 PDF with audit trail; enable version history.
Notification cadence, reminders, and escalation rules Set reminders at configurable intervals and notify stakeholders upon signature.

Where to send or file a completed SUP1

Common submission paths for a completed SUP1 include the contract repository, project management system, finance function, and stakeholder distribution channels.

  • Contract Repository: Upload signed PDF to the contract management system.
  • Project Management Tool: Attach SUP1 to the project record in PM software.
  • Finance / Billing: Send invoice-linked SUP1 to accounts payable for reconciliation.
  • Stakeholder Distribution: Distribute final copy to all approvers and archive recipients.

Technical requirements for digital SUP1 execution

Digital execution requires platform support for PDF and DOCX files, secure storage, audit trails, and integration with project tools.

  • File types: PDF and Word DOCX formats supported
  • Integrations: Salesforce, Microsoft 365, NetSuite, Procore, Box
  • Security: AES-256 at rest; TLS 1.2/1.3 in transit

Common SUP1 timelines and expected processing windows

Key deadlines and expected processing times guide SUP1 submissions, internal approvals, vendor acceptance, and invoicing reconciliation to keep projects on schedule.

Draft prepared by PM:

Typically within 3 business days after change identification.

Internal review period:

Allow 5–10 business days for legal and finance review.

Approvals and signatures:

Target 1–5 business days when using eSignature.

Vendor acknowledgement:

Vendor responses often return within 7–14 calendar days.

Invoice reconciliation:

Finance reconciles payments within the billing cycle, normally 30 days.

Sequential milestones from request to archival

Sequential milestone stages outline SUP1 processing from initial request through approval, implementation, verification, and archival to ensure traceable progress.

01

Request Submitted

Change request logged and SUP1 drafted.

02

Internal Review

PMO and legal assess scope and cost impacts.

03

Signatures Obtained

All approvers sign; capture audit trail and timestamps.

04

Archive and Close

Store signed SUP1 in contract repository and notify stakeholders.

Key data elements required on the SUP1

Document ID: Unique alphanumeric reference code
Effective Date: Enter date as MM/DD/YYYY
Party Names: Enter full legal entity names
Scope Summary: Provide one-sentence scope summary
Signatures: Typed or electronic signature with date
Attachments: Attach exhibits, drawings, and change logs

Common mistakes to avoid when preparing a SUP1

  • Incomplete identifiers lead to misfiled supplements, lost traceability, and delays in linking the SUP1 to the correct contract or project record.
  • Ambiguous scope descriptions cause disputes; failing to list exclusions or assumptions invites differing interpretations among stakeholders.
  • Missing approval sequence or absent signatures result in unapproved scope changes and possible billing disputes or withheld payments.
  • Uploading unsigned drafts to the repository without an audit trail undermines enforceability and complicates audits and dispute resolution.

Risks and potential consequences of an incorrect SUP1

Contractual Disputes: Potential breach claims and litigation risk.
Delay Claims: Schedule extensions and liquidated damages exposure.
Payment Withholding: Invoices could be rejected or withheld.
Regulatory Noncompliance: Permit or audit violations in regulated projects.
Audit Findings: Missing audit trail triggers compliance issues.
Tax Implications: Incorrect billing affects tax reporting.

Real-world examples of SUP1 usage

Sample customer scenarios show how organizations use electronic SUP1 templates to accelerate approvals and keep auditable records.

Martin Properties — Tim Martin

Tim Martin needed remote execution for lease-related project changes.

  • SUP1 used to capture vendor deliverables and payment changes.
  • "I can process and execute all of these documents online with 100% compliance and built-in security. Whether on mobile or working offline, I can get forms back to their necessary parties efficiently."

Xerox — Kodi-Marie Evans

Xerox integrated SUP1s into its NetSuite workflows for signature routing.

  • Integration ensured correct formats and tracking.
  • "airSlate SignNow provides us with the flexibility needed to get the right signatures on the right documents, in the right formats, based on our integration with NetSuite."

Representative eSignature pricing and capability comparison

Sample vendor pricing and capability snapshot for executing SUP1 documents electronically; signNow is listed first per platform comparison conventions.

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 plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes Varies by plan
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 using and signing SUP1

Answers to common questions about electronic execution, notarization, retention, and error correction for SUP1 documents 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.