Can a SUP2 be signed electronically?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Exceptions exist for testamentary documents and certain court filings; confirm that the SUP2 does not fall into statutory exceptions.

Do SUP2 forms require notarization?

Most SUP2s do not require notarization unless local contracting rules or the contract specifically demand it. If notarization is needed, verify whether remote online notarization is permitted in your state.

What authentication is recommended for signers?

Use at least email link plus optional SMS code for routine approvals. For higher assurance or regulatory sensitivity, use multi-factor or knowledge-based authentication.

How should attachments be formatted?

Supply attachments as PDF or flattened PDF/A where possible, include a brief index, and ensure filenames reference the SUP2 ID to avoid version confusion during review.

Who verifies signer authority?

The initiating project manager verifies delegated signing authority before routing. Maintain a record of delegation limits in contract files to simplify audits.

How to correct an approved SUP2?

Create an amended SUP2 referencing the original SUP2 ID and clearly state the corrective changes. Route the amendment through the same approval flow to maintain a continuous audit trail.

Electronic Signature
Templates
Project Management
Project Management SUP2 Form

Project Management SUP2 Form

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

PROJECT MANAGEMENT SUP2 FORM

Project Identification

Project Title:

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

Recitals and Effective Date

This SUP2 Form documents supplemental agreement and amendment to the existing Project Agreement between Client Name: and Service Provider: .

Effective Date:

Scope of Work

Detailed Scope of Work Out of Scope

Deliverables and Acceptance

List of key deliverables, each with acceptance criteria. Acceptance by the Client constitutes formal sign-off against the criteria specified.

Deliverable 1 — Title Acceptance Criteria Deliverable 2 — Title Acceptance Criteria

Timeline and Milestones

Project Start Date: Project End Date:

Milestone 1

Date: Owner:

Milestone 2

Date: Owner:

Budget and Payment

Total Contract Value Payment Schedule Change Order / Variation Process

Dependencies, Risks & Resourcing

Key Dependencies Resource Requirements

Confidentiality

The parties acknowledge that during performance they may exchange Confidential Information. Confidential Information shall be used only for the purposes of performing under this SUP2 and shall not be disclosed except as expressly permitted by written agreement or required by law.

Both parties acknowledge and agree that Confidential Information protections apply as described above.

Governing Law and Dispute Resolution

This SUP2 shall be governed by the laws of the jurisdiction indicated below. Any dispute arising under this SUP2 that cannot be resolved by negotiation shall be submitted to the dispute resolution process set forth by the parties.

Governing Jurisdiction

Approvals and Certifications

By signing below, each signatory represents and warrants that they are duly authorized to bind the party on whose behalf they sign, that the information provided in this SUP2 is complete and accurate to the best of their knowledge, and that the party will comply with the terms herein.

Certification (Client):

Certification (Provider):

Signatures

Client (Printed Name):

By:

Date:

Title/Role:

Service Provider (Printed Name):

By:

Date:

Title/Role:

What the Project Management SUP2 Form Is

The Project Management SUP2 Form is a supplemental project document used to record scope changes, schedule adjustments, cost impacts, approvals, and supporting attachments for an ongoing project. It standardizes how change requests and supplemental instructions are captured, routed, and archived so stakeholders have a single, auditable record of amendments to baseline project documents.

Why the SUP2 Form Matters for Project Control

Using a consistent SUP2 form reduces ambiguity about scope and cost, preserves an approval history, and helps teams resolve disputes faster by producing a discrete, dated record of every project change.

Who Typically Prepares and Signs a SUP2 Form

Clear role assignment on the form reduces rework and speeds downstream procurement, billing, and scheduling tasks.

Project managers and PMO staff who document scope changes and manage approvals.
Contractors and subcontractors who confirm cost and schedule impacts for proposed changes.
Owners or client representatives who must authorize budgetary or scope modifications.

Who Signs and What Their Role Is

Project Manager

The Project Manager completes the SUP2 with change description, schedule and cost impacts, and internal approvals. They track routing, confirm resource availability, and retain the approved copy in the project record for audit and closeout.

Contracting Officer

The Contracting Officer or authorized procurement representative reviews cost and contract impact, certifies funding where required, and signs to bind the organization to the updated scope and payment terms.

Core Sections Found on a Professional SUP2 Form

A well-structured SUP2 captures change details, impacts, approvals, and attachments so reviewers can assess risk quickly and consistently.

Change Summary

Concise description of the work or deliverable being added, removed, or revised, including reference to the original contract line or task.

Schedule Impact

Clear statement of days or milestones affected and any critical-path consequences for deliverable dates.

Cost Impact

Itemized cost increase or decrease with a subtotal, taxes, and any contingency or markup calculations shown.

Approval Block

Designated signature lines for each authorized party, with role, date, and printed name to establish authority and attribution.

Attachments

Reference supporting documents such as revised drawings, RFI responses, estimates, or vendor quotes attached and indexed.

Record ID

Unique SUP2 identifier and related project codes to ensure traceability in project management and financial systems.

Step-by-Step: Completing a SUP2 Form

Follow these four steps to prepare, approve, and file a SUP2 without common delays.

01

Gather Evidence: Collect drawings, RFIs, quotes, and schedule data supporting the change.
02

Complete Form: Fill mandatory fields, attach documents, and calculate cost and schedule effects.
03

Route for Approval: Send to required approvers in the established order for review and signatures.
04

Archive Record: Store the signed SUP2 in the project repository and notify finance and scheduling teams.

Typical Digital Workflow Settings for SUP2 Processing

Configure these settings when turning the SUP2 into a repeatable eWorkflow to reduce manual handoffs.

Field	Setting
Authentication Method	Email link \| SMS code \| KBA as needed for higher assurance
Signature Type	Typed or drawn signature \| Optional PKI for high-assurance records
Routing Order	Sequential routing \| Parallel for non-dependent approvals
Reminder Interval	3 days \| Automated reminders until signature obtained

How Digital Submission and Signing Works

An electronic workflow reduces transit time and creates an auditable trail for every SUP2 transaction.

Upload Document: Import completed SUP2 and attachments into the signing platform.
Place Fields: Add signature, date, and conditional fields to the form.
Send to Signers: Dispatch via email link or secure signing portal to designated approvers.
Capture Audit Trail: Platform records timestamps, IPs, and authentication events for compliance.

Platform and File Requirements for eSubmission

Confirm storage location and retention settings to meet internal records and regulatory needs.

File Formats: PDF, DOCX, and flattened PDF/A are commonly supported.
Integrations: Salesforce, Microsoft 365, NetSuite, and Google Workspace are typical integrations.
Authentication: Email link, SMS code, or stronger methods where policy requires.

eSignature Pricing Snapshot for SUP2 Workflows

Compare common pricing and capability dimensions when choosing a signing provider for SUP2 forms; signNow is listed first per platform comparisons.

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

Security and Compliance Features to Expect

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Audit Trail: Detailed timestamp and event logging

Certifications: SOC 2 Type II, ISO 27001

HIPAA: BAA available for protected health information

ESIGN / UETA: Compliant with U.S. electronic signature laws

Accessibility: WCAG 2.0 Level AA support

Key Risks and Financial Consequences

Missing Signature: Contract not enforceable until properly signed

Incorrect Amounts: Can lead to billing disputes and change claims

1099 Exposure: Penalties up to $330 per form for late/incorrect filing

I-9 Noncompliance: Civil penalties range $281–$2,789 per violation

Data Breach: Regulatory fines and remediation costs possible

Unauthorized Approval: Potential breach of procurement rules and contract

Common Errors That Delay SUP2 Approval

Incomplete cost breakdowns that omit tax, contingency, or unit-rate calculations causing reviewers to request clarifications.
Unclear or unreferenced change descriptions that fail to tie the SUP2 to a specific drawing, RFI, or contract clause.
Wrong signatory listed or signer lacking delegated authority, forcing re-routing and voiding approvals.
Attaching large unindexed files or unsupported formats which prevent reviewers from opening or validating supporting documents.

Practical Tips to Reduce SUP2 Friction

Adopt these practices to shorten approval cycles and maintain audit-ready records.

Use a Unique Identifier

Assign a SUP2 number and include project code consistently across systems so finance and scheduling teams can correlate change records immediately.

Attach Compact Evidence

Attach only relevant pages, label each file, and reference the attachment in the change description to make review straightforward.

Pre-Validate Calculations

Reconcile cost impacts to unit rates and existing change history before routing to approvals to avoid back-and-forth queries.

Define Approval Limits

Use role-based approval thresholds so small changes can be approved quickly while larger modifications follow a higher-authorization path.

How Teams Use SUP2 Forms in the Field

Real-world examples show how SUP2 forms speed approvals, reduce disputes, and maintain traceable records across stakeholders.

Martin Properties

The team converted paper change orders to an eSUP2 workflow to cut turnaround time by days.

They used templated cost fields and attachments for consistency.
As a result, they reduced approval back-and-forth and maintained a single audit trail for closeout and owner reporting.

Xerox (NetSuite Ops)

NetSuite integration allowed auto-populated project IDs and vendor rates into SUP2 forms.

This eliminated duplicate entry and calculation errors.
The integration ensured SUP2 approvals triggered accounting entries and reduced month-end reconciliation effort for project managers.

Frequently Asked Questions About SUP2 Forms

Answers to common legal, technical, and process questions teams ask when adopting SUP2 forms and eSign workflows.

Need help? Contact support

Can a SUP2 be signed electronically?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Exceptions exist for testamentary documents and certain court filings; confirm that the SUP2 does not fall into statutory exceptions.
Do SUP2 forms require notarization?
Most SUP2s do not require notarization unless local contracting rules or the contract specifically demand it. If notarization is needed, verify whether remote online notarization is permitted in your state.
What authentication is recommended for signers?
Use at least email link plus optional SMS code for routine approvals. For higher assurance or regulatory sensitivity, use multi-factor or knowledge-based authentication.
How should attachments be formatted?
Supply attachments as PDF or flattened PDF/A where possible, include a brief index, and ensure filenames reference the SUP2 ID to avoid version confusion during review.
Who verifies signer authority?
The initiating project manager verifies delegated signing authority before routing. Maintain a record of delegation limits in contract files to simplify audits.
How to correct an approved SUP2?
Create an amended SUP2 referencing the original SUP2 ID and clearly state the corrective changes. Route the amendment through the same approval flow to maintain a continuous audit trail.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now