Is an electronic signature valid for an addon?

Yes. Under the federal ESIGN Act (15 U.S.C. §7001) and UETA in most states, electronic signatures are legally valid when the parties demonstrate intent, consent, attribution, and retained records.

When is notarization required?

Notarization is not generally required for commercial contract amendments, but some states or specific contract clauses may require an acknowledged signature or witness; confirm the parent contract and local law.

Can I use a simple typed signature?

A typed or drawn signature can be sufficient if intent and attribution are clear and the platform records an audit trail; regulated transactions may require stronger authentication or cryptographic signatures.

How should executed addons be stored?

Store executed addons with the parent contract in a secure repository, retain searchable metadata, and preserve the audit trail for the duration required by federal or industry regulations.

Are health-related addons subject to HIPAA?

If the addon involves protected health information, treat it under HIPAA rules and retain records for 6 years from creation or last effective date (45 CFR §164.530(j)); obtain necessary business associate agreements.

What if signer names differ from IDs?

Mismatched signer names can create enforceability or payment issues; require signers to use their legal name as shown on government ID and include role/title to clarify authority.

Electronic Signature
Templates
Miscellaneous
Beach Pebble Project Addon

Beach Pebble Project Addon

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

BEACH PEBBLE PROJECT ADDON

This Addon ("Addon") is entered into by and between Client Name: and Contractor Name: .

Project Reference: Original Agreement Date:

WHEREAS

WHEREAS, the parties entered into an agreement identified by the Project Reference and Original Agreement Date above (the "Original Agreement"); and

WHEREAS, Client has requested and Contractor has agreed to perform certain additional services and deliverables related to the Beach Pebble Project described in this Addon; and

WHEREAS, the parties desire to amend the scope, schedule, and payment terms of the Original Agreement solely as set forth in this Addon; now, therefore, in consideration of the mutual promises herein, the parties agree as follows:

SCOPE OF ADDON

Contractor shall perform the additional services and provide the additional deliverables described below. All services shall conform to professional industry standards and the specifications set forth by Client in writing.

Describe Addon Scope and Deliverables Estimated Completion for Addon

PAYMENT TERMS

The parties agree that compensation for the Addon shall be as set forth below. Fees due under this Addon are in addition to amounts under the Original Agreement unless specifically stated otherwise.

Total Additional Amount Payment Schedule

Invoice Due (days)

Late Fee

Retainer Required

Yes No

TERM AND TERMINATION

This Addon shall commence on Start Date: and shall terminate on End Date: unless earlier terminated in accordance with this Addon.

Notice Period for Termination Termination Effects

CONFIDENTIALITY

Each party shall maintain in confidence all non-public information disclosed by the other party in connection with this Addon ("Confidential Information"). Confidential Information shall not include information that is or becomes generally available to the public other than through a breach of this Addon, or that was already in the receiving party's possession prior to disclosure as demonstrated by written records.

The receiving party shall use Confidential Information solely for the performance of this Addon and shall not disclose Confidential Information to any third party except to employees, consultants, or contractors who have a need to know and who are bound by confidentiality obligations no less protective than those herein. Upon termination or written request, the receiving party shall return or destroy Confidential Information as directed by the disclosing party.

GOVERNING LAW

This Addon shall be governed by and construed in accordance with the laws of the Jurisdiction: , without regard to principles of conflict of laws. The parties submit to the exclusive jurisdiction of the courts of that jurisdiction for disputes arising under this Addon.

ENTIRE AGREEMENT

Except as expressly modified by this Addon, the Original Agreement remains in full force and effect. This Addon, together with the Original Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior negotiations, representations, and agreements, whether written or oral. In the event of any conflict between the terms of this Addon and the Original Agreement, the terms of this Addon shall control.

MISCELLANEOUS

No amendment, modification, or waiver of any provision of this Addon shall be effective unless in a written instrument signed by both parties. If any provision of this Addon is held unenforceable, the remaining provisions shall remain in full force and effect.

Notices required under this Addon shall be sent to the addresses below or to such other address as a party may designate in writing.

Client Address for Notices Contractor Address for Notices

Client:

By:

Date:

Contractor:

By:

Date:

What the Beach Pebble Project Addon Is

The Beach Pebble Project Addon is a formal amendment used to record changes to an existing project contract, including scope adjustments, material substitutions, schedule updates, or incremental work orders tied to a primary agreement. It establishes the revised obligations, pricing, and timelines between the original parties and functions as an enforceable contract amendment when executed by authorized signatories. The Addon typically references the parent contract, identifies affected line items, and defines whether the change is additive, substitutive, or corrective to the original scope of work.

Why a Structured Addon Matters for Project Control

A clear, signed addon reduces disputes by documenting exactly what changes, costs, and deadlines apply. It protects both parties by confirming authorization, preserving contract continuity, and creating an audit trail for approvals and payments.

Typical Users and Stakeholders

The Beach Pebble Project Addon is used by project managers, contractors, property owners, and procurement teams to implement controlled changes to an active contract.

Project managers and contractors who need to record scope or schedule changes and obtain client acceptance quickly.
Owners and developers who require written authorization for extra work, cost adjustments, or substituted materials.
Procurement and accounting teams who need documented basis for change invoices, payments, and budget reconciliation.

Each stakeholder uses the addon to verify authorization, update schedules, and record financial adjustments before work continues.

Core Elements of a Professional Addon

A professional addon combines unambiguous scope language with price detail, revised schedule milestones, party authorizations, and signature blocks so changes are actionable and auditable.

Scope Summary

Concise description of the specific work added, removed, or modified, tied to original contract sections and applicable drawings or specifications.

Pricing Detail

Itemized cost changes, unit rates, allowances, and subtotal with clear notation of whether the amount is an estimate, fixed price, or not-to-exceed figure.

Schedule Impact

Updated milestone dates or completion deadlines, plus any liquidated damages or extension-of-time provisions linked to the change.

Authorization

Name, title, and capacity of the individual approving the change on behalf of each party, with company affiliation and contact details.

Reference Data

Parent contract identifier, amendment number, relevant clause citations, and attachments (drawings, RFIs, material specs) incorporated by reference.

Signatures

Execution blocks for each authorized signatory showing printed name, title, date, and witness or notary lines if required by law or contract.

Step-by-Step: How to Complete and Approve an Addon

Follow these steps to prepare, review, and finalize a Beach Pebble Project Addon with clarity and legal validity.

01

Draft the Change: Document the scope, costs, and schedule adjustments in plain language.
02

Attach Evidence: Include drawings, RFIs, quotes, and approvals that justify the change.
03

Route for Review: Share the draft with technical, legal, and finance reviewers for concurrence.
04

Execute and Archive: Collect signatures, record the addon with contract file, and distribute executed copies.

Configuring an Online Addon Workflow

Below are common configuration settings used when managing addons in an electronic workflow or eSignature platform.

Field	Configuration
Document Template	Use a locked template that pulls parent contract ID automatically.
Required Fields	Mark Parent Contract, Effective Date, Cost, and Signatures as required.
Reviewer Order	Set sequential approvals: Project Manager → Legal → Finance.
Retention Tags	Apply metadata for contract number and retention period at finalization.

Where to Send and How to Distribute the Executed Addon

Routing an executed addon correctly ensures accounting, project teams, and procurement all have a single authoritative copy.

Primary Contract File: Store executed addon with the parent contract record in your contract repository.
Finance: Send a copy to accounts payable to trigger invoicing and payment adjustments.
Project Team: Notify field supervisors and schedulers to implement scope or timeline changes.
Procurement: Update purchase orders and material release schedules when applicable.

Digital Signing and Submission Considerations

Use an eSignature platform that preserves an audit trail, supports required authentication, and produces a tamper-evident final document.

Authentication: Email, SMS code, or stronger methods as required.
Audit Trail: Must record IP, timestamp, and signer actions.
Document Formats: Support for PDF and DOCX is typical.

Typical Timing and Response Expectations

Establish clear deadlines for proposal submission, internal review, approval, and execution to prevent project delays.

Change Proposal Window:

Submit change requests within 7 calendar days of discovering the issue.

Internal Review:

Allow 5–10 business days for technical and legal review depending on complexity.

Client Approval:

Expect client decision within 10–14 calendar days unless expedited.

Execution Deadline:

Signatures should be collected within 30 calendar days to avoid stale pricing.

Work Commencement:

Do not begin changed work until the addon is fully executed unless written provisional authorization exists.

Key Milestones From Request to Implementation

A sequential milestone view helps coordinate approvals and field scheduling for addon work.

01

Request Submitted

Originator submits detailed change request with supporting documents for review.

02

Technical Review

Engineering or site team assesses scope, impact, and cost implications.

03

Contract Approval

Authorized representatives approve cost and schedule changes and execute the addon.

04

Implementation

Field teams receive updated instructions and begin changed work per revised schedule.

Common Mistakes to Avoid When Preparing an Addon

Vague scope language that omits measurable deliverables or references to drawings, creating ambiguity during execution and payment.
Failing to tie the addon to the parent contract ID and amendment number, which complicates accounting and dispute resolution.
Not clarifying whether price adjustments include taxes, permits, or contingency costs, leading to billing disputes.
Proceeding with changed work before execution, which can forfeit contract protections or trigger nonpayment claims.

Risks and Consequences of an Improperly Executed Addon

Payment Disputes: Unclear or unsigned addons increase the risk of withheld payments and prolonged invoicing disputes.

Schedule Claims: Lack of documented schedule adjustments can result in acceleration claims or liquidated damages exposure.

Contract Termination: Unauthorized scope changes may be treated as breach, giving the other party termination rights.

Regulatory Noncompliance: Certain public works or licensed work may require specific approvals; failure can trigger fines or stop-work orders.

Audit Deficiencies: Incomplete records hinder audits and may affect insurance or bonding claims.

Notarization Errors: If a jurisdiction or contract requires notarization, missing or incorrect notarization can render the addon unenforceable.

Vendor Pricing and Feature Snapshot for eSignature Support

The table compares starting prices and core capabilities for common eSignature vendors to help match platform features with addon processing 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	Yes, 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
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently Asked Questions About the Addon

Answers to common questions about validity, signing, storage, and state-specific concerns when using a Beach Pebble Project Addon.

Need help? Contact support

Is an electronic signature valid for an addon?
Yes. Under the federal ESIGN Act (15 U.S.C. §7001) and UETA in most states, electronic signatures are legally valid when the parties demonstrate intent, consent, attribution, and retained records.
When is notarization required?
Notarization is not generally required for commercial contract amendments, but some states or specific contract clauses may require an acknowledged signature or witness; confirm the parent contract and local law.
Can I use a simple typed signature?
A typed or drawn signature can be sufficient if intent and attribution are clear and the platform records an audit trail; regulated transactions may require stronger authentication or cryptographic signatures.
How should executed addons be stored?
Store executed addons with the parent contract in a secure repository, retain searchable metadata, and preserve the audit trail for the duration required by federal or industry regulations.
Are health-related addons subject to HIPAA?
If the addon involves protected health information, treat it under HIPAA rules and retain records for 6 years from creation or last effective date (45 CFR §164.530(j)); obtain necessary business associate agreements.
What if signer names differ from IDs?
Mismatched signer names can create enforceability or payment issues; require signers to use their legal name as shown on government ID and include role/title to clarify authority.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now