Can the DC be electronically signed?

Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states, provided intent, consent, attribution, and record retention requirements are satisfied.

When is notarization required?

Notarization is required only if state law or the contract mandates it. For certain deeds or statutory filings, a notary or RON may be necessary; verify with the contracting authority.

What if signers’ names differ?

Mismatched names can raise enforceability questions. Always use full legal names and confirm authority; attach evidence of delegation if signing on behalf of an entity.

How long to retain executed DCs?

Retain for the active term plus at least three years; follow applicable federal rules such as IRC §6501(a) for tax records and HIPAA 45 CFR §164.530(j) for health information.

Are audit trails sufficient?

A detailed audit trail (timestamps, IP addresses, signer emails) supports attribution and retention requirements under ESIGN/UETA and is generally sufficient absent industry-specific cryptographic requirements.

What authentication level is recommended?

Use email or SMS for low-risk approvals; require stronger authentication or KBA for high-value change orders or government procurements to reduce fraud risk.

Electronic Signature
Templates
Project Management
Project Management Supplemental DC

Project Management Supplemental DC

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

PROJECT MANAGEMENT SUPPLEMENTAL DC

Project Identification

Project Title Project ID Client Name Client Contact (Name, Title, Phone / Email) Service Provider Name Project Manager (Provider)

Effective Date of this Supplemental Agreement:

Recitals and Amendment

This Project Management Supplemental DC (the Supplemental) amends the existing agreement between Client and Service Provider identified above (the Agreement). Except as expressly modified herein, all terms and conditions of the Agreement remain in full force and effect. This Supplemental is incorporated into and forms part of the Agreement as of the Effective Date specified above.

Scope of Work (SOW) — Supplemental Changes

Detailed Description of Supplemental Scope Items Specifically Out of Scope (if any)

Deliverables and Acceptance

Deliverable 1 Title: Due Date:

Acceptance Criteria for Deliverable 1

Deliverable 2 Title: Due Date:

Acceptance Criteria for Deliverable 2

If additional deliverables are required, Parties shall execute a Change Order in accordance with the Change Order Process below.

Timeline and Milestones

Project Start Date: Project End Date:

Milestone 1 (Description)

Milestone 1 Due Date:

Milestone 2 (Description)

Milestone 2 Due Date:

Budget, Fees and Payment

Total Supplemental Cost Payment Schedule

Retainage or holdback (if any):

Change Order Process

All changes to scope, schedule, or price shall be executed only by a written Change Order signed by authorized representatives of both Parties. Service Provider shall submit a written Change Order proposal containing a description of the change, impact on schedule, and a cost proposal. Client shall accept or reject in writing within days of receipt; failure to respond constitutes rejection.

Standard Change Order Rate (if applicable)

Acceptance Testing and Remedies

Upon completion of each deliverable, Client shall have calendar days to perform acceptance testing and either accept the deliverable in writing or provide a written list of deficiencies. Provider shall correct deficiencies at Provider's expense within a reasonable time commensurate with the severity of the deficiency.

Confidentiality and Data Handling

Each Party shall maintain the confidentiality of the other's Confidential Information and shall not disclose such information except to its employees, agents, or subcontractors who have a need to know and are bound by confidentiality obligations at least as protective as those herein. Confidentiality obligations shall survive termination of this Supplemental for months.

Liability, Indemnity and Insurance

Each Party shall indemnify, defend and hold harmless the other from claims arising out of its negligence or willful misconduct in connection with this Supplemental. Except as to willful misconduct or breaches of confidentiality, neither Party's liability shall exceed the direct fees paid under this Supplemental for the specific scope giving rise to the claim.

Termination and Notices

Either Party may terminate this Supplemental for convenience upon days' prior written notice. Termination for cause shall be effective upon written notice if the defaulting Party fails to cure within a reasonable cure period specified in the notice.

Governing Law and Dispute Resolution

This Supplemental shall be governed by and construed in accordance with the laws of the District of Columbia without regard to conflict-of-law principles. The Parties shall attempt in good faith to resolve disputes promptly by negotiation between senior representatives. If unresolved, disputes shall be resolved by binding arbitration or litigation as agreed in the Agreement.

Miscellaneous

This Supplemental, together with the Agreement and any executed Change Orders, constitutes the entire understanding between the Parties with respect to the subject matter hereof. No amendment to this Supplemental is effective unless made in writing and signed by authorized representatives of both Parties.

Administrative Information

Billing Address for Client Billing Address for Service Provider

Client Printed Name:

By:

Date:

Title/Authority:

Service Provider Printed Name:

By:

Date:

Title/Authority:

What the Project Management Supplemental DC Is

The Project Management Supplemental DC is a structured addendum used to record project-specific terms, schedules, responsibilities, and deliverables that augment a primary project agreement. It standardizes scope descriptions, milestone definitions, change order procedures, payment triggers, and approval authorities so project teams and stakeholders share a common operational reference. The supplemental form is typically attached to a master contract or purchase order and is used throughout execution to approve scope changes, confirm milestone completion, and track deliverable acceptance without reissuing the primary agreement.

Why a Supplemental DC Matters for Project Controls

A formal supplemental document reduces ambiguity about scope, timing, and signatory authority, which lowers disputes and helps enforceable acceptance criteria.

Typical Parties Who Complete the Supplemental DC

Accurate completion by these roles ensures the supplemental DC functions as an effective operational extension of the primary contract.

Project Manager — Documents scope details, milestones, acceptance criteria and coordinates sign-offs across teams.
Procurement/Contracting — Verifies contractual alignment, procurement references, payment terms, and supplier compliance.
Subcontractor Representative — Confirms deliverables, resource availability, and change order acceptance before signing.

Core Components of a Professional Supplemental DC

A complete supplemental DC clearly defines scope, schedule, responsibilities, acceptance standards, change procedures, and payment terms so contractual intent is unambiguous.

Scope Summary

Concise description of work included and explicitly excluded so deliverables and boundaries are clear to all parties.

Milestone Schedule

Dated milestones with acceptance criteria and deliverable owners to measure progress and trigger payments or reviews.

Roles & Authority

Named contacts, signing authority limits, and escalation points to ensure approvals follow contractual delegation.

Change Control

Procedure for submitting, pricing, approving, and documenting change orders to prevent scope creep and disputes.

Payment Terms

Clear invoicing schedule, retainage, and acceptance conditions that tie payment releases to milestone verification.

Acceptance Criteria

Quantitative or qualitative tests and required documentation that define when a deliverable is officially accepted.

Stepwise Process to Complete and Approve the Supplemental DC

Follow these sequential steps to draft, review, approve, and archive the supplemental DC so it is enforceable and accessible.

01

Draft: Populate scope, milestones, and payment terms from the project plan.
02

Internal Review: Legal and procurement review for contractual alignment and risk mitigation.
03

Counterparty Review: Send to vendor or subcontractor for confirmation and edits.
04

Execution: Collect authorized signatures and store executed copy in the project repository.

How to Configure a Digital Approval Workflow

Set up an electronic workflow that maps reviewers, required fields, and signing order to mirror your organization’s approval process.

Field	Configuration
Routing Order	Sequential or parallel routing based on approval hierarchy.
Required Fields	Mark name, date, and milestone confirmations as required before routing continues.
Authentication	Choose email, SMS code, or advanced signer authentication per risk profile.
Audit Capture	Enable full audit trail with timestamps and IP addresses for each action.

Typical Digital Execution Flow for the Supplemental DC

Digital execution follows a predictable lifecycle: upload, place fields, route, sign, and archive.

Upload Document: Add the completed supplemental DC to the signing platform as a PDF or DOCX.
Place Fields: Insert signature, date, and checkbox fields where required.
Send to Signers: Route to designated signers in the configured order or via a signing link.
Complete & Archive: Collect signatures, capture audit trail, and save final copy to records.

Platform and Integration Considerations for eSubmission

Ensure the chosen system can export signed records with an audit trail and store them in your document management system for retention compliance.

Integrations: Salesforce, NetSuite, Microsoft 365 and Project tools are commonly required.
File Formats: PDF and DOCX support is essential for templates and final storage.
Authentication: Email, SMS, KBA, or SSO options to match risk profiles.

Security and Compliance Essentials

Encryption: TLS 1.2/1.3 in transit

Data at Rest: AES-256 encryption

Certifications: SOC 2 Type II, ISO 27001

HIPAA: BAA available

Audit Trail: Detailed timestamps and IPs

Accessibility: WCAG 2.0 Level AA

Common Timing and Processing Expectations

Understand required delivery dates and statutory timelines that commonly affect supplemental documents and their consequences.

Delivery on Request:

Supply W-9 or vendor info promptly when requested; no fixed statutory deadline applies.

1099-NEC Deadlines:

Issue to recipients and IRS by Jan 31 each year for payments reporting.

Tax Filing:

Individual Form 1040 due April 15; extension to Oct 15 with Form 4868.

I-9 Retention:

Retain I-9 for 3 years after hire or 1 year after termination, whichever is later (8 CFR §274a.2).

Change Order Response:

Specify internal SLA for response time in the DC, typically 5–15 business days.

Common Mistakes to Avoid When Preparing the Supplemental DC

Using vague acceptance criteria that prevent objective verification and delay payment approvals.
Failing to name authorized signers, resulting in signatures that lack enforceable authority.
Omitting referenced exhibits or schedules, which creates disputes over what was promised.
Not aligning milestone dates to the project baseline, causing scheduling and cashflow mismatches.

Risks and Potential Consequences of Errors

Incorrect Tax Filings: Penalties per form

I-9 Violations: $281–$2,789 per violation

Contract Disputes: Delay claims and additional legal costs

Unauthorized Signatures: Possible unenforceability

Missing Records: Noncompliance with audits

Intentional Misreporting: Higher fines, no cap

eSignature Vendor Pricing Snapshot for Supplemental DC Workflows

Comparison of common vendor price points and envelope or usage constraints to help align platform selection with project volume and compliance needs.

	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	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
Envelope Cap	No cap	100/year	Varies by plan	Varies by plan	Varies by plan

Practical Examples of Supplemental DC Use

Real-world examples show how teams use supplemental DCs to speed approvals and reduce disputes.

Optica Ventures

A small development firm standardized milestone descriptions to reduce ambiguity.

Saved two weeks per project approval cycle.
Consistent templates improved handoffs and reduced payment disputes by clarifying acceptance tests and payment triggers for all subcontractors.

Tech Data

A large reseller added formal change-order pricing tables to the supplemental DC.

Faster internal approvals for scope changes.
The change-control table allowed procurement and finance to approve variations quickly, which shortened billing cycles and improved forecasting accuracy across multiple vendor engagements.

Frequently Asked Questions and Troubleshooting

Answers to common questions about completion, digital signing, retention, and signatory authority for the supplemental DC.

Need help? Contact support

Can the DC be electronically signed?
Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states, provided intent, consent, attribution, and record retention requirements are satisfied.
When is notarization required?
Notarization is required only if state law or the contract mandates it. For certain deeds or statutory filings, a notary or RON may be necessary; verify with the contracting authority.
What if signers’ names differ?
Mismatched names can raise enforceability questions. Always use full legal names and confirm authority; attach evidence of delegation if signing on behalf of an entity.
How long to retain executed DCs?
Retain for the active term plus at least three years; follow applicable federal rules such as IRC §6501(a) for tax records and HIPAA 45 CFR §164.530(j) for health information.
Are audit trails sufficient?
A detailed audit trail (timestamps, IP addresses, signer emails) supports attribution and retention requirements under ESIGN/UETA and is generally sufficient absent industry-specific cryptographic requirements.
What authentication level is recommended?
Use email or SMS for low-risk approvals; require stronger authentication or KBA for high-value change orders or government procurements to reduce fraud risk.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now