Establishing secure connection…Loading editor…Preparing document…

Project Management Additive Use Agreement

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

PROJECT MANAGEMENT ADDITIVE USE AGREEMENT

This Project Management Additive Use Agreement (the Agreement) is entered into effective as of by and between the parties identified below.

Project Identification

Definitions and Purpose

For purposes of this Agreement, "Additive Use" means the incorporation, application, or integration of additive materials, components, processes, or manufactured items into project deliverables, whether by additive manufacturing techniques, chemical additives, proprietary materials, or other process-driven inclusions. Client authorizes Service Provider to employ Additive Use only as expressly described in the Scope of Work and pursuant to the terms and conditions set forth herein.

Scope of Work

Deliverables and Acceptance

Service Provider will deliver the following deliverables incorporating Additive Use. Each deliverable must meet the stated acceptance criteria and pass the acceptance procedure before Client is deemed to have accepted the deliverable.

Proposed delivery date for Deliverable 1:

Proposed delivery date for Deliverable 2:

Timeline and Milestones

Project Start Date:

Project End Date:

Milestone 1 Date:

Budget and Payment

Change Order Process

All changes affecting Additive Use, scope, schedule, or price shall be documented in a written change order signed by authorized representatives of both parties. No change will be effective until a change order is executed.

Testing, Compliance and Acceptance Procedures

Service Provider shall perform or procure all testing necessary to demonstrate that Additive Use meets the acceptance criteria. Testing protocols, pass/fail criteria, and sampling methods shall be documented and provided to Client in advance of acceptance testing. Client shall have a specified review period of calendar days from delivery of results to accept or reject a deliverable in accordance with the Acceptance Criteria.

Warranties, Liability and Indemnity

Service Provider represents and warrants that all Additive Use shall conform to the Scope of Work, shall be free from material defects in workmanship and materials for a period of from final acceptance. Except as expressly set forth herein, Service Provider disclaims other warranties. Each party shall indemnify and hold harmless the other from third-party claims arising from its negligent acts or willful misconduct in connection with Additive Use, subject to any agreed limitations of liability set forth below.

Confidentiality

Each party shall treat as Confidential Information all non-public information disclosed in connection with the Project, including technical specifications, process parameters, proprietary additive formulations, and test results. Confidential Information shall not be disclosed except as required by law or with the prior written consent of the disclosing party. Confidentiality obligations shall survive termination for a period of years.

Regulatory Compliance and Safety

Service Provider shall ensure that all Additive Use complies with applicable laws, codes, and industry standards. Service Provider shall provide Material Safety Data Sheets and other safety documentation for additive materials upon Client request and shall follow accepted handling and disposal practices for such materials.

Termination

Either party may terminate this Agreement for material breach if the other party fails to cure the breach within thirty (30) days after written notice. Upon termination, Client shall pay for work performed and documented costs reasonably incurred up to the termination effective date, subject to applicable offsets for defective work or unremedied performance failures.

Intellectual Property

Unless otherwise agreed in writing, Service Provider retains ownership of background intellectual property and proprietary process know-how used to perform the Services. Title to project-specific deliverables incorporating Additive Use shall be as set forth in the separate IP terms below or, absent such terms, transferred to Client upon full payment, subject to Service Provider's perpetual license to its background technology.

Governing Law and Dispute Resolution

This Agreement shall be governed by and construed in accordance with the laws of without regard to conflict of law principles. The parties agree to attempt good faith negotiation prior to pursuing litigation; remedies shall be as provided by law and this Agreement.

Miscellaneous

This Agreement embodies the complete agreement between the parties with respect to Additive Use and supersedes prior negotiations and understandings. Amendments must be in writing and signed by authorized representatives of both parties.

Client

Client Name:

By:

Date:

Service Provider

Service Provider Name:

By:

Date:

Enter text✕

What the Project Management Additive Use Agreement Is

The Project Management Additive Use Agreement is a written contract that documents changes, additions, or amendments to an existing project scope, schedule, or deliverables. It records the additional work description, pricing or rates, revised milestones, approvals, and any adjusted warranties or acceptance criteria. The agreement is typically attached to the original contract as an additive or change order and identifies the parties, the effective date, and the method for resolving disputes. Properly executed addenda reduce ambiguity, establish responsibility for extra costs, and provide a clear audit trail for project controls and invoicing.

Why a Clear Additive Agreement Matters

A Project Management Additive Use Agreement protects both parties by documenting scope changes, cost adjustments, and timelines, making project accountability explicit and enforceable under contract law and electronic signature statutes such as the ESIGN Act (15 U.S.C. ch. 96) and state UETA rules.

Why a Clear Additive Agreement Matters

Who Typically Prepares and Signs This Additive Agreement

Project managers, contract administrators, general contractors, and client procurement or vendor managers commonly prepare and execute additive use agreements to record authorized scope changes.

  • Project Managers and PMOs who track scope, schedule, and deliverables for active projects.
  • Procurement and Contract Administrators responsible for approvals, budget control, and compliance.
  • General Contractors, Subcontractors, or Vendors who will perform and bill for the added work.

Legal counsel, finance, and quality managers frequently review significant addenda to verify compliance with procurement policies, budget authority, and regulatory or industry requirements.

Primary Signatories and Their Roles

Client Authorized Signer

An officer or procurement designee with express authority to accept changes and approve budget impacts. This signer confirms that funds or contingency allowances exist and that the change is authorized under the original contract terms.

Contractor Representative

A project lead or authorized company officer who accepts the revised scope, delivers the amended schedule, and acknowledges any adjusted costs, warranties, and acceptance criteria on behalf of the performing party.

Core Elements to Include in Every Additive Agreement

A professional Project Management Additive Use Agreement is concise but complete: identify parties, reference the original contract, detail the additive scope, state pricing and payment terms, set new milestones, and include signature blocks and governing law.

Reference Clause

Cite the original contract by title, date, and section to make the additive clearly linked and avoid ambiguity about which contract provisions remain in force.

Detailed Scope

Describe the additional tasks, deliverables, and acceptance criteria in measurable terms so performance can be verified and invoiced without dispute.

Price and Payment

State a fixed amount or a clear rate schedule, payment milestones, invoice timing, and any retainage or withholding terms tied to the additive work.

Schedule Changes

List adjusted start and completion dates, critical-path impacts, and any agreed extensions to liquidated damages or performance milestones.

Risk Allocation

Specify responsibility for permits, inspections, additional insurance, delay costs, and indemnities related to the additive scope.

Signatures and Authority

Include printed names, titles, dates, and any required witness or notarization language to confirm signatory authority and execution date.

Step-by-Step: Completing the Additive Agreement

Follow these sequential steps to prepare, approve, and finalize an addendum that is complete and enforceable.

  • 01
    Draft Addendum: Describe added work, attach change documents and referenced drawings.
  • 02
    Estimate Cost: Calculate labor, materials, overhead, and contingency explicitly.
  • 03
    Obtain Approvals: Secure written approval from authorized client and contractor representatives.
  • 04
    Execute and Distribute: Have all signatories sign, date, and circulate final copies to stakeholders.

Typical Routing and Approval Workflow

Addenda commonly flow through a defined routing path to ensure budget approval and operational readiness before work begins.

  • Initiation: Project lead identifies change and creates a draft addendum.
  • Review: Contracts and finance teams review cost and terms for policy compliance.
  • Approval: Authorized signers execute the addendum and confirm funding.
  • Distribution: Execute copies are provided to PM, procurement, field teams, and accounting.

Configuring an Online Approval Workflow

When automating addendum approvals, set fields and routing to mirror your internal authorization matrix and accounting controls.

Field Configuration
Approval Order Sequential — Project Manager > Contracts > Finance
Signer Authentication Email + SMS code for external signers; SSO for internal users
Document Retention Auto-archive signed PDF to contract repository
Notifications Email reminders at 3 and 7 days for pending signatures

Digital Signing and Technical Requirements

Ensure your eSignature provider supports legal compliance, audit trails, and the integrations your teams use.

  • Authentication: Email+code, SMS, or enterprise SSO; stronger options recommended for high-value changes.
  • Audit Trail: Capture timestamps, IP addresses, and action logs for enforceability.
  • Integrations: Connect to storage and ERP (Salesforce, NetSuite, Box, Google Workspace).

Security and Compliance Essentials for Additive Agreements

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Audit Trail: Immutable event log with timestamps and signer attribution
HIPAA: BAA required when handling PHI
21 CFR Part 11: Support for timestamping and controlled access for FDA records
ESIGN / UETA: Compliant for electronic execution and admissibility
SOC 2 / ISO: SOC 2 Type II and ISO 27001 attestations available

Key Legal Risks and Financial Consequences

Unapproved Work: May be unpaid or disputed by client
Late Notice: Liquidated damages or schedule penalties apply
Incorrect Tax Reporting: IRS penalties may apply for improper invoicing
I-9 Noncompliance: Employment verification fines possible
Contract Breach: Damages, termination, or indemnity claims
Recordkeeping Failures: Regulatory sanctions or audit findings

Common Preparation Pitfalls to Avoid

  • Failing to reference the original contract increases ambiguity about governing terms and payment responsibility.
  • Using vague scope language (e.g., 'work as needed') invites disputes over deliverables and acceptance.
  • Not documenting funding or approval authority can leave contractors exposed to unpaid work.
  • Omitting updated schedule impacts can trigger liquidated damages or missed milestone payments.

Best Practices for Clear, Enforceable Addenda

Follow these practical steps to reduce disputes and ensure the additive is effective and enforceable.

Be Specific
Use measurable deliverables, reference drawings by revision, list quantities, and attach supporting documents so scope is self-contained and verifiable.
Link to Funding
Document budget approvals, purchase orders, or contingency draws to demonstrate authority and payment source for added costs.
Keep Versions
Assign sequential addendum numbers and store executed copies with the original contract to preserve an audit trail.
Use Standard Forms
Adopt a consistent addendum template that includes clauses for change order procedure, dispute resolution, and governing law.

Typical Deadlines and Timing Considerations

Key dates in an addendum affect when work can begin, when invoices are due, and how long records must be kept for regulatory compliance.

Effective Date:

Start date for added obligations (MM/DD/YYYY).

Work Commencement:

Date when field or services are authorized to proceed.

Invoice Submission:

Invoice window tied to milestones or completion events.

Payment Terms:

Net terms (e.g., Net 30) or milestone payments defined.

Record Retention:

Retain executed copies per applicable legal retention rules.

Key Milestones from Request to Closed Addendum

A typical lifecycle includes initiation, approval, performance, inspection, and closure; each milestone affects billing and compliance.

01

Request Submitted

Change request captured with scope and cost estimate.

02

Internal Review

Contracts and finance validate price and authority.

03

Client Approval

Authorized signer executes addendum and funds are committed.

04

Work Completed

Contractor performs added work and documents deliverables.

Comparing eSignature Vendors for Executing Addenda

Choose an eSignature provider that meets security, compliance, and integration needs; the table below summarizes basic plan and compliance differences among common vendors.

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 vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Real-World Examples of Addenda in Practice

These condensed examples show how different organizations document additive changes and the outcomes that follow.

Construction Change Order

A general contractor documented a scope increase for site grading using an addendum with unit pricing

  • The addendum included a revised schedule and retainage clause
  • The clear pricing and approval sequence avoided a payment dispute and aligned field teams with the new completion date.

Healthcare Vendor Amendment

A hospital amended a service agreement to add telehealth support with data handling terms

  • The amendment attached a BAA and PHI safeguards
  • This avoided regulatory exposure and ensured vendor liability coverage while enabling rapid service rollout.

Frequently Asked Questions

Answers to common questions about preparing, signing, and storing a Project Management Additive Use Agreement.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users