Can this addendum be electronically signed?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Ensure the signer consents to electronic records and the platform preserves an auditable record.

Who must sign the addendum?

The authorized signatory listed in the master agreement or SOW should sign. Verify signer authority in the contract to avoid challenges to enforceability or payment.

What if the client rejects the hours?

If the client refuses approval, do not start the additional work. Document the dispute, seek clarification, and follow the contract’s change-control process to resolve scope and billing.

Is notarization required for this form?

Not typically for ordinary SOW addenda. Only seek notary or RON if the contract or a specific jurisdiction requires acknowledgment for the type of amendment being executed.

How should hours be recorded after approval?

Track hours in the project timesheet tied to the approved addendum. Retain signed addendum and timesheets as part of the billing backup for audits and invoicing.

Can the addendum be revised after signing?

Yes, but any revision should be documented with a new amendment or written change order signed by the same authorized parties to avoid ambiguity in obligations.

Electronic Signature
Templates
Project Management
Project Management Additional PM and UX Time

Project Management Additional PM and UX Time

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

Project Management Additional PM and UX Time

Project Identification

Project Title Project ID Client Name Service Provider Project Manager

Purpose and Authorization

This document authorizes Additional PM and UX Time for the project identified above. Client Name: hereby approves the described additional services to be performed by Service Provider: in accordance with the terms and rates set forth below.

Scope of Additional Work

Detailed Scope of PM and UX Activities Out-of-Scope Items

Deliverables and Acceptance

Deliverable 1 — Description:

Acceptance Criteria

Deliverable 2 — Description:

Acceptance Criteria

Timeline and Milestones

Proposed Start Date: Proposed End Date:

Milestone 1

Target Date:

Milestone 2

Target Date:

Budget, Rates and Payment

Estimated Additional PM Hours: PM Hourly Rate: $

Estimated Additional UX Hours: UX Hourly Rate: $

Estimated Total Additional Cost Payment Schedule Change Order Process

I acknowledge that additional work beyond this authorization requires a signed change order and may be billed at the rates above. Acknowledge

Confidentiality and Proprietary Rights

All information exchanged under this authorization is subject to the confidentiality obligations of the underlying master services agreement. The Service Provider shall not disclose Client confidential information to any third party and shall use such information solely for the performance of the authorized additional work. All deliverables produced under this authorization will be considered work for hire and, unless otherwise specified in writing, ownership of final deliverables will transfer to the Client upon full payment.

Liability, Remedies and Governing Law

Except as expressly provided in this authorization and any controlling agreement between the parties, each party's aggregate liability for claims arising from this authorization shall be limited to amounts actually paid for the additional work. Neither party will be liable for consequential or special damages. This authorization shall be governed by the laws of the state of without regard to conflict of law principles.

Acknowledgment of Scope and Fees

By signing below, the parties acknowledge and agree that the additional scope, estimated hours, rates and payment terms set forth in this authorization are accepted and authorized. Invoicing will occur in accordance with the Payment Schedule above and payments are due according to the controlling agreement.

Client Name:

By:

Date:

Service Provider:

By:

Date:

What this Project Management Additional PM and UX Time form is

The Project Management Additional PM and UX Time is a formal change-addendum that documents requests for extra project management and user experience effort beyond an original scope. It records the requested additional hours, the rationale, rate or pricing, schedule impact, and approvals from client and internal stakeholders. The document functions as an auditable record to align expectations, update billing, and authorize work before extra effort is performed. It is typically attached to the underlying master services agreement or statement of work so that the change is incorporated into the contractual record.

Why teams use an additional PM and UX time addendum

A clear addendum reduces scope disputes by documenting extra hours, cost, and schedule impact before work begins. It helps billing accuracy and preserves project governance.

Who completes and signs this addendum

Typical participants include internal project and UX leads plus the client's authorized approver who confirm scope, hours, and fees.

Project Manager — Prepares scope description and hours estimate, tracks approvals and schedule impact.
UX Lead — Details user research or design tasks, justifies hours, and confirms deliverables affected.
Client Approver — Authorized representative who agrees to additional cost, schedule changes, and signs for acceptance.

Keep approvers to the roles listed in the original agreement to avoid invalid signatures or billing disputes.

Core elements to include in a professional addendum

A well-structured addendum clearly ties the request to the original contract, quantifies work, states rates, and records signer authority and effective dates.

Scope Addendum

Concise description of the additional PM and UX tasks, referencing original SOW section numbers or deliverables to avoid ambiguity.

Hours Requested

Number of additional PM and UX hours requested per role with task-level breakdown to support billing and scheduling.

Rate Table

Hourly rates or fixed fees per role, including any overtime rates, expenses policy, and currency designation.

Schedule Impact

Estimated changes to milestone dates, critical path items affected, and any contingency for further delay.

Approvals

Designated signers, their titles, and explicit signature blocks that record date and printed name for attribution.

Reference Links

Contract reference (SOW/PO number), attachment list, and versioning to ensure clear contract integration.

Required information and essential fields

Project Name: Full project identifier

Requestor: Name and role of originator

Hours Breakdown: PM hours | UX hours

Rates: Hourly rates and currency

Effective Date: MM/DD/YYYY format

Signatures: Printed name, title, date

Stepwise process to complete and approve the addendum

Follow a short review and approval sequence so work does not start before authorization and billing terms are clear.

01

Draft Request: Prepare scope, hours, rates and schedule impact in the addendum.
02

Internal Review: Obtain PM and finance sign-off for cost and resource availability.
03

Client Approval: Send to the client's authorized approver for signature and date.
04

Archive Record: Attach to original SOW and store signed copy per retention policy.

How to configure an online workflow for this addendum

Configure an online template to automate fields, routing, and approvals for consistent, traceable change requests.

Field	Configuration
Authentication	Email plus optional SMS code for signer verification
Conditional Fields	Show hours and rate fields only when 'Additional Work' checked
Auto-calc Total	Formula field multiplies hours by rate for each role
Template Library	Save approved template to shared library for reuse

Typical routing for online submission and approval

A simple arrow workflow speeds approvals: prepare, route for approval, sign, and store with an audit trail.

Upload: Attach the addendum to the master SOW or select template
Assign: Route to PM, finance, and client approver in order
Sign: Client signs electronically; platform captures timestamp
Store: Save signed PDF and metadata to project repository

Digital signing and platform needs

Use a platform that supports secure e-signatures, audit trails, and the document formats your team uses.

File Formats: PDF and DOCX supported
Integrations: Salesforce, NetSuite, Google Workspace
Authentication: Email, SMS, or advanced options

Ensure the chosen system preserves an immutable audit trail (timestamps, IP, signer identity) and supports role-based access controls for secure storage.

Common timelines and internal deadlines to track

Define and communicate deadlines for submission, internal approval, client decision, and billing to avoid unapproved work or delayed invoices.

Submission Window:

Submit change request within 30 days of scope change

Internal Approval:

Allow 3–5 business days for PM and finance review

Client Decision:

Client approval expected within 10 business days

Billing Adjustment:

Apply approved charges on the next invoice cycle

Archive Timing:

Store signed addendum within 48 hours of execution

Common risks and consequences of incomplete or incorrect addenda

Unauthorized Work: Client may refuse payment

Billing Errors: Invoices disputed or delayed

Scope Creep: Uncontrolled additional effort

Contract Conflict: Ambiguity leads to disputes

Compliance Gaps: HIPAA or data rules violated

Audit Exposure: Insufficient records for review

eSignature vendor comparison relevant to approving addenda

Compare baseline pricing and core capabilities for common eSignature providers. signNow is listed first; confirm plan details with each vendor before purchasing.

	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	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently asked questions about the addendum

Answers to common questions about execution, e-signing, signatory authority, and next steps after approval.

Need help? Contact support

Can this addendum be electronically signed?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Ensure the signer consents to electronic records and the platform preserves an auditable record.
Who must sign the addendum?
The authorized signatory listed in the master agreement or SOW should sign. Verify signer authority in the contract to avoid challenges to enforceability or payment.
What if the client rejects the hours?
If the client refuses approval, do not start the additional work. Document the dispute, seek clarification, and follow the contract’s change-control process to resolve scope and billing.
Is notarization required for this form?
Not typically for ordinary SOW addenda. Only seek notary or RON if the contract or a specific jurisdiction requires acknowledgment for the type of amendment being executed.
How should hours be recorded after approval?
Track hours in the project timesheet tied to the approved addendum. Retain signed addendum and timesheets as part of the billing backup for audits and invoicing.
Can the addendum be revised after signing?
Yes, but any revision should be documented with a new amendment or written change order signed by the same authorized parties to avoid ambiguity in obligations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now