Are electronic signatures legally valid?

Yes. The ESIGN Act (15 U.S.C. ch. 96) and UETA in most states make electronic signatures enforceable when intent to sign, consent to an electronic record, attribution of the signature, and reliable record retention are present.

When is notarization required for an add-on?

Notarization is required only when state law or the document type dictates it (for example, certain property-related instruments). Remote online notarization (RON) is broadly available but state-specific; verify identity-proofing and recording rules before relying on RON.

How do I confirm signer authority?

Confirm signer authority with a corporate resolution, power of attorney, or other corporate documentation. Capture signer title and contact details in the packet and retain proof of authorization to reduce risk of later challenges.

Can I use add-on packets that include PHI?

If the packet contains protected health information, ensure a Business Associate Agreement is in place with any vendor handling PHI and follow HIPAA retention and access rules (see 45 CFR §164.530(j)). Obtain patient consent as required.

What if a packet was signed with an error?

Do not alter an executed packet. Execute a corrective addendum or replacement packet, both signed by authorized parties, and retain the original with a note referencing the correction; preserve the audit trail for both documents.

Which file formats and exports are supported?

Commonly supported formats include PDF, Word (DOCX), Excel, and HTML. For long-term archiving, export the signed record as PDF/A and keep the audit trail or certificate of completion with the stored file.

Client Add-On Packet

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

CLIENT ADD-ON PACKET

Client and Packet Identification

Client Name Client Billing Address Primary Contact Master Agreement / Account Number Add-On Packet Number

Effective Date:

Recitals

WHEREAS, Client and Service Provider are parties to a Master Services Agreement dated (the "Agreement"), which governs provision of services and payment; and

WHEREAS, Client requests additional services, materials, or modifications described herein (the "Add-On Services") that are not included within the current scope of the Agreement; and

WHEREAS, Provider is willing to perform the Add-On Services subject to the terms and conditions of this Client Add-On Packet, which shall modify the Agreement only as expressly set forth below.

Scope of Work

The Provider shall provide the Add-On Services described below. The description shall be incorporated into the Agreement upon execution of this Add-On Packet.

Detailed Description of Add-On Services

Itemized Add-Ons and Costs

Check the specific add-ons to be added to the Agreement and provide the associated cost. Provider will not commence billed work for unchecked items.

Add-On Item 1 Amount:

Add-On Item 2 Amount:

Add-On Item 3 Amount:

Estimated Total for Selected Add-Ons

Payment Terms

Client shall pay Provider for the Add-On Services in accordance with the following payment terms. All fees are non-refundable unless otherwise stated in writing and are subject to the terms of the Agreement.

Amount for Add-On Services Payment Schedule Invoice Due Days Late Fee

Any unpaid amounts are subject to the late fee stated above, applied monthly on unpaid balances, and Provider may suspend performance until past due amounts are cured.

Term and Termination

The Add-On Services shall commence on and shall continue until , unless earlier terminated in accordance with this Add-On Packet or the Agreement.

Notice Period for Termination

Termination for material breach shall follow the cure and notice provisions of the Agreement; termination for convenience may be exercised by either party only if expressly indicated below.

Termination for Convenience (select if applicable) I hereby elect termination for convenience rights for this Add-On Packet.

Confidentiality

Each party acknowledges that it may receive Confidential Information of the other. For purposes of this Add-On Packet, "Confidential Information" means nonpublic business, technical and financial information disclosed in connection with the Add-On Services. Each party agrees to (a) hold the other's Confidential Information in confidence using at least the same degree of care it uses to protect its own confidential information but in no event less than reasonable care; (b) not disclose such Confidential Information to any third party except as permitted under the Agreement; and (c) use Confidential Information solely to perform rights and obligations under this Add-On Packet. The confidentiality obligations in the Agreement remain in full force and effect for information exchanged under this Add-On Packet.

Governing Law

This Add-On Packet shall be governed by and construed in accordance with the laws of the jurisdiction selected by the parties. State/Country:

Entire Agreement; Incorporation

This Add-On Packet, together with the Agreement and any other documents expressly incorporated herein, constitutes the entire agreement of the parties with respect to the subject matter of this Add-On Packet. Except as expressly modified by this Add-On Packet, all terms and conditions of the Agreement remain unchanged and in full force and effect. In the event of any inconsistency between this Add-On Packet and the Agreement, the terms of this Add-On Packet shall control only to the extent of such inconsistency.

Representations; Authorization

Each party represents and warrants that it has the full corporate or individual power and authority to enter into and perform its obligations under this Add-On Packet and that the person signing below is authorized to execute this Add-On Packet on behalf of that party.

Attachments

List of Attachments or Exhibits Incorporated by Reference

By signing below the parties agree that the Add-On Services described herein are authorized and that the terms of this Add-On Packet shall be legally binding upon execution.

Client:

By:

Date:

Provider:

By:

Date:

What the Client Add-On Packet Is and When It Applies

The Client Add-On Packet is a signed attachment to an existing client agreement that documents additional services, scope changes, pricing adjustments, and client authorizations. It pairs concise amendment language with defined deliverables, timelines, and charge schedules so both parties have a clear record of expectations. Organizations use add-on packets to formalize upgrades, select optional features, or confirm one-off work without drafting a full contract amendment. When executed electronically under applicable U.S. law, the packet becomes a binding component of the client agreement.

Why a Structured Add-On Packet Matters for Contracts

Use a Client Add-On Packet to record scope changes, set fees, and obtain client consent quickly while preserving the original contract. It reduces ambiguity, supports billing accuracy, and creates an auditable record suitable for electronic execution under ESIGN and state e-signature laws.

Which Roles Typically Prepare or Sign an Add-On Packet

Account managers, project leads, legal teams, and client representatives commonly prepare or sign a Client Add-On Packet to document changes.

Account managers: authorize scope additions, pricing changes, and schedule updates with client signatures.
Legal teams: review amendment language, confirm compliance with existing contract terms, and clear risk or liability clauses.
Clients or signers: confirm acceptance of added services, fees, and revised completion or delivery dates with an authorized signature.

Retain executed packets with the master agreement and distribute copies to billing and project management to ensure enforceability and correct invoicing.

Core Elements to Include in a Professional Add-On Packet

A professional Client Add-On Packet includes clear scope, pricing, timeline, signature blocks, references to the master agreement, and required approvals.

Scope

Describe additional deliverables and exclusions precisely; include acceptance criteria and measurable outcomes so parties can verify completion against the amended scope without reverting to the original contract text.

Pricing

List fees, billing frequency, payment terms, and any one-time charges; specify whether existing retainers apply, how taxes are handled, and who bears reimbursable expenses, and note late payment penalties.

Timeline

Specify effective date, milestone dates, delivery windows, and any expedited timelines; state whether timelines supersede or supplement dates in the master agreement and include cure periods for delays.

Signatures

Provide signature blocks for all parties with printed name, title, and date; identify authorized signers and include witness or notary lines where state law or internal policy requires them.

References

Cite the master agreement by date and section number, indicate whether the packet amends or supplements that agreement, and include a cross-reference clause to avoid conflicting terms.

Approvals

Include routing for internal approvals, checklist of required signatures, and a field for legal review; record version number and approver names to maintain auditability of changes.

Four Steps to Prepare, Approve, and File an Add-On Packet

Follow this four-step sequence to complete, approve, and file a Client Add-On Packet efficiently while preserving legal validity and auditability.

01

Prepare: Draft add-on scope, pricing, and dates.
02

Review: Legal and finance confirm terms and fees.
03

Sign: Authorized parties execute with required authentication.
04

Distribute: File with contract record; notify billing and PM.

Configuring an Online Workflow for Add-On Packets

Configure an online add-on workflow to automate field placement, signer routing, and conditional approvals for efficient processing.

Field	Configuration
Signer Authentication	Email links, SMS codes, or KBA as required.
Conditional Fields	Show fields based on service selections to reduce errors.
Notifications	Auto-notify billing, PM, and legal on execution.
Document Storage	Save PDF/A with audit trail to cloud archive.

Typical Submission and Processing Steps in an eWorkflow

Typical routing steps for submitting and processing a Client Add-On Packet through an electronic workflow and audit trail.

Upload: Attach final packet PDF to the workflow.
Place Fields: Add signature, date, and text fields.
Send to Signers: Designate signer order or allow parallel signing.
Archive: Store signed packet and certificate of completion.

Technical Considerations for Digital Distribution

Electronic distribution relies on secure file formats, signer authentication, and integrations with billing or contract repositories.

File Formats: PDF, DOCX, and fillable PDF/A supported.
Integrations: Salesforce, NetSuite, Microsoft 365 integrations available.
Auth Options: Email link, SMS code, or SSO possible.

Typical Timelines and Deadlines for Add-On Processing

Common timing expectations and deadlines when issuing or processing a Client Add-On Packet in typical project workflows.

Request and Preparation Deadline:

Allow 3–7 business days for drafting and internal review.

Client Review Period:

Standard 5–10 business days unless expedited by agreement.

Execution Deadline:

Set a firm sign-by date to avoid scope ambiguity.

Billing Effective Date:

Specify whether charges begin on execution or on an agreed service date.

Retention Start Date:

Retention usually begins on effective date or invoice date, whichever is later.

Common Preparation Errors to Avoid

Vague scope descriptions that omit acceptance criteria lead to disputes over deliverables and invoice challenges; always include measurable criteria and referenced exhibits.
Missing or incorrect signer authority—using a contact who lacks corporate signing power—can render the add-on unenforceable and delay billing or work.
Inconsistent dates between the add-on packet and the master agreement cause conflicts; ensure effective and termination dates align or explicitly state which document controls.
Failing to route the executed packet to billing and project management results in missed invoices and implementation gaps; include clear distribution fields and automation.

Risks and Consequences of an Incorrect or Incomplete Packet

Contract Disputes: Ambiguity can trigger breach claims.

Billing Delays: Invoices may be postponed.

Tax Reporting: Incorrect fee allocation affects 1099 reporting.

Regulatory Noncompliance: Failure to obtain required consents can violate rules.

HIPAA Exposure: Missing BAA for PHI workflows creates risk.

Notary Invalidity: Improper notarization may void execution.

eSignature Pricing and Feature Comparison for Add-On Packet Workflows

Compare baseline eSignature pricing and feature availability for handling Client Add-On Packets; signNow is listed first in the vendor column order as required.

	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	Varies
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Real-World Examples of Add-On Packet Use

These brief examples show how organizations apply add-on packets to streamline approvals and preserve contractual clarity.

Optica Ventures LLC

Optica uses add-on packets to formalize small service upgrades across clients and maintain consistent contract terms.

The interface is simple and easy-to-use for our team.
Standardized packets reduced administrative friction, improved customer clarity on scope and fees, and lowered the number of follow-up clarifications needed for each change.

Fertility Centers of Illinois

The center adopted electronic add-on packets for patient authorizations and fee acknowledgments to reduce in-person paperwork.

The team has been exceptional, responsive, the API has been great.
Electronic packets preserved secure audit trails for consent, accelerated administrative processing, and simplified remote patient interactions while maintaining required recordkeeping and security controls.

Frequently Asked Questions and Practical Answers

Answers to common questions about signature validity, notarization, signer authority, HIPAA considerations, corrections, and supported formats for Client Add-On Packets.

Need help? Contact support

Are electronic signatures legally valid?
Yes. The ESIGN Act (15 U.S.C. ch. 96) and UETA in most states make electronic signatures enforceable when intent to sign, consent to an electronic record, attribution of the signature, and reliable record retention are present.
When is notarization required for an add-on?
Notarization is required only when state law or the document type dictates it (for example, certain property-related instruments). Remote online notarization (RON) is broadly available but state-specific; verify identity-proofing and recording rules before relying on RON.
How do I confirm signer authority?
Confirm signer authority with a corporate resolution, power of attorney, or other corporate documentation. Capture signer title and contact details in the packet and retain proof of authorization to reduce risk of later challenges.
Can I use add-on packets that include PHI?
If the packet contains protected health information, ensure a Business Associate Agreement is in place with any vendor handling PHI and follow HIPAA retention and access rules (see 45 CFR §164.530(j)). Obtain patient consent as required.
What if a packet was signed with an error?
Do not alter an executed packet. Execute a corrective addendum or replacement packet, both signed by authorized parties, and retain the original with a note referencing the correction; preserve the audit trail for both documents.
Which file formats and exports are supported?
Commonly supported formats include PDF, Word (DOCX), Excel, and HTML. For long-term archiving, export the signed record as PDF/A and keep the audit trail or certificate of completion with the stored file.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now