Is an electronic signature legally enforceable?

Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted in most states), electronic signatures are generally valid if intent, consent, attribution, and record retention requirements are met. Certain documents remain excluded from e-signature rules.

When is notarization or witness required?

Notarization is not routinely required for device agreements, but some states or specific transaction types may require notarization or witnesses. Remote Online Notarization (RON) rules vary by state; verify with state notary commission or counsel before relying on RON.

What authentication is recommended for signers?

Use email plus an additional factor for higher-risk transactions. For sensitive data or regulatory contexts, consider SMS codes, knowledge-based authentication, or advanced signer authentication. Document the chosen method and ensure the audit trail captures IP, timestamp, and signer attribution.

Can the agreement be modified after signing?

Yes, by mutual written amendment. Amendments should be dated, signed by authorized parties, and reference the original agreement. Use an addendum or replacement agreement; maintain both original and amendment copies together for audit and legal clarity.

How should signed records be stored?

Store signed agreements in encrypted repositories with access controls, regular backups, and retention policies. Ensure the system can reproduce the record and audit trail for litigation or compliance. Follow HIPAA, IRS, or state retention rules as applicable.

What common errors invalidate agreements?

Common errors include mismatched signer names, missing dates, absent consent disclosures for consumer-facing records, incomplete authentication logs, and storing only image signatures without an audit trail. Correct errors by re-executing amended documents with proper evidence.

Electronic Signature
Templates
Miscellaneous
Mobile Companion Agreement

Mobile Companion Agreement

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

Mobile Companion Agreement

This Mobile Companion Agreement (the Agreement) is entered into as of by and between:

Client Name:

Service Provider / Companion Name:

Recitals

WHEREAS, Client seeks companionship and non-medical supportive services that may require travel to locations selected by the Client or mutual agreement, and desires to retain Companion to provide such services; and

WHEREAS, Companion represents that Companion is qualified and available to provide mobile companion services, and is willing to perform such services for compensation under the terms and conditions set forth herein; and

NOW, THEREFORE, in consideration of the mutual covenants contained herein, the parties agree as follows:

Scope of Work

Description of Services

Services may include, without limitation: companionship, transportation to appointments or social activities, accompaniment on errands, light assistance with mobility, conversation, and other non-medical assistance as described above. Companion shall not perform medical acts, invasive personal care, or services requiring a licensed health-care professional unless separately agreed and documented.

Payment Terms

Base Rate (per hour or per visit) Payment Schedule Invoicing and Method of Payment Late Fee Travel & Reimbursement

If travel is required, Client shall reimburse Companion for reasonable travel expenses as set forth above. Companion is responsible for maintaining records of travel and submitting receipts or mileage logs as requested.

Term and Termination

Term Commencement Date: Term Expiration Date:

Notice Period for Termination

Either party may terminate this Agreement without cause upon written notice to the other party as provided above. Either party may terminate immediately for cause if the other party materially breaches this Agreement and fails to cure the breach within a reasonable period not to exceed 14 days after written notice specifying the breach.

Confidentiality

Companion acknowledges that in the course of performing services Companion may receive or observe information concerning Client's personal affairs, health, financial matters, or other confidential information. Companion agrees to keep all such information strictly confidential and not to disclose it to any third party except as required by law or with Client's prior written consent. Confidential information does not include information that: (a) is or becomes publicly available other than by breach of this Agreement; (b) is rightfully received from a third party without restriction; or (c) is independently developed by Companion without use of or reference to Client's confidential information.

Liability; Insurance; Independent Contractor

Companion shall perform services as an independent contractor and not as an employee of Client. Companion is solely responsible for all taxes, insurance, and benefits related to Companion's personnel and operations. To the extent permitted by law, Companion shall maintain general liability insurance or other coverage appropriate to the services provided and shall furnish proof of insurance upon Client's request.

Except to the extent caused by willful misconduct or gross negligence, each party's liability under this Agreement shall be limited to direct damages not to exceed the total amount paid by Client to Companion under this Agreement during the preceding six (6) months. Neither party shall be liable for special, incidental, consequential, exemplary, or punitive damages.

Background Screening and Compliance

Background Check Authorization

If Client requires background screening, Companion consents to reasonable screenings and verifications. Companion shall comply with all applicable laws, ordinances, and regulations in performing services hereunder.

Cancellation Policy

Cancellation Terms

Unless otherwise agreed, cancellations made less than 24 hours before a scheduled visit may be subject to a cancellation fee equivalent to one hour's base rate or as otherwise specified in the Payment Terms.

Governing Law; Dispute Resolution

Governing State Law

This Agreement shall be governed by and construed in accordance with the laws of the state specified above, without regard to its conflict of law principles. The parties shall first attempt to resolve disputes through good-faith negotiation. If unresolved, disputes shall be resolved by binding arbitration in accordance with the arbitration laws of the governing state, unless the parties mutually agree otherwise in writing.

Entire Agreement; Amendments

This Agreement constitutes the entire agreement between the parties regarding the subject matter hereof and supersedes all prior or contemporaneous written or oral agreements, representations, and understandings. This Agreement may be amended or modified only by a written instrument signed by both parties.

Additional Provisions

Emergency Contact Special Instructions or Client Preferences

The parties acknowledge that no guarantee of continuance of hours or visits is made except as expressly set forth in this Agreement. Companion may decline any assignment that Companion reasonably determines to present an unacceptable risk.

Client:

By:

Date:

Service Provider:

By:

Date:

What the Mobile Companion Agreement Covers

The Mobile Companion Agreement is a standardized contract that governs use, access, and responsibilities related to a mobile device, application, or support service provided to an individual or employee. It sets terms for permitted uses, data access, security obligations, maintenance responsibilities, and liability allocation. The agreement typically addresses ownership, lost or damaged devices, updates, acceptable use policies, and remote management capabilities. It can be used by employers, service providers, and vendors to document expectations and protect sensitive data when mobile devices interact with corporate systems or handle regulated information.

Why a clear Mobile Companion Agreement matters

A Mobile Companion Agreement clarifies responsibilities, reduces device-related risk, and documents data protection measures. It helps organizations enforce acceptable use, allocate costs for repairs or replacements, and demonstrate compliance with privacy and security obligations when mobile devices access regulated systems.

Who typically uses this agreement

Employers, IT departments, managed service providers, human resources, and independent vendors who supply or manage mobile devices or companion apps commonly use this agreement.

Employers and HR teams documenting device allowances, responsibilities, and return policies for staff.
IT and security teams setting access controls, remote wipe authority, and app installation rules.
Service providers and vendors outlining support terms, data handling, and liability limits.

Use the agreement as a clear operational and legal record to reduce disputes, support audits, and meet regulatory obligations.

Key signer roles and responsibilities

IT Director

Typically authorizes device configuration, security controls, and remote management. Responsible for enforcing acceptable-use rules, coordinating wipe or reconfiguration after termination, and recording technical details necessary for incident response or compliance audits.

Device User

Signs to acknowledge receipt, acceptable use, and data access permissions. Responsible for routine care, reporting loss/theft promptly, and complying with privacy and security obligations. Misuse can result in disciplinary action and potential liability for damage or data breaches.

Core sections to include in the agreement

Core sections of a Mobile Companion Agreement define permitted uses, security controls, support responsibilities, data handling, liability, and termination procedures for mobile devices and companion services.

Permitted Use

Specifies authorized activities, business vs personal use distinctions, and prohibited actions such as sideloading apps or bypassing security controls. Clear scope reduces ambiguity and enforcement disputes.

Security Controls

Details required device protections: device encryption, passcode policies, patching cadence, and approved MDM/EMM software. Assigns responsibility for applying updates and monitoring security posture. Includes logging and reporting obligations.

Support & Repairs

Defines who provides device support, service windows, replacement policies for lost or damaged devices, and cost allocation for repairs or upgrades, including whether employee reimbursement is required.

Data Handling

Specifies data collection, storage, encryption, backup, and permitted third-party sharing. Requires compliance with HIPAA or other industry-specific privacy standards when protected data is involved and documents responsibilities for breach notification.

Liability & Indemnity

Allocates risk between parties, limits liability, and sets indemnification obligations for data breaches, negligence, or willful misconduct. Exclusions and caps should be clearly defined and include procedures for claims handling.

Termination

Specifies conditions for device return, data retention and deletion procedures, and the effects of termination on ongoing obligations such as license grants or support commitments.

Step-by-step: complete and execute the agreement

Follow these steps to complete and execute the Mobile Companion Agreement accurately using an electronic workflow.

01

Prepare Document: Gather device details, parties, effective date, and attachments.
02

Configure Fields: Add signature, date, and conditional fields for returns.
03

Select Signers: Assign roles and authentication level per signer.
04

Execute & Archive: Sign, capture audit trail, and store final copy securely.

Configure the digital signing workflow

Configure the online workflow to enforce field validation, signer authentication, and automated routing for the Mobile Companion Agreement.

Workflow Field Name for Setup	Configuration
Signature Field	Mandatory signature with date validation
Conditional Return Field	Displays return instructions if device flagged lost
Authentication Level	Email or SMS code; use KBA for higher risk
Attachment Requirement	Require proof of purchase or insurance when applicable

Platform capabilities for eSubmission and storage

Ensure the eSignature platform supports secure storage, audit trails, and configurable authentication to meet legal and compliance requirements for mobile device agreements.

File Formats: PDF and DOCX supported
Integrations: Connectors for MDM, HRIS, and CRM
Authentication: Email, SMS, SAML SSO

Where signed agreements are sent and stored

Typical destinations and routing for executed Mobile Companion Agreements, including email distribution, secure storage, and HR/IT intake.

Send to HR: Email signed copy to HR records mailbox
IT Archive: Store document in encrypted asset management system
User Copy: Provide signer with final PDF and audit trail
Third-Party: Share redacted copy with insurers or support vendors

Key dates to track

Key dates to track when issuing, renewing, or enforcing a Mobile Companion Agreement across organizational processes.

Agreement Effective Date and Activation:

Enter start date as MM/DD/YYYY and record deployment events.

Annual Review and Renewal Window:

Schedule periodic reviews and set automatic renewal reminders sixty to ninety days prior.

Loss or Theft Reporting Deadline:

Report device loss within 24–48 hours to enable remote wipe and insurance claims.

Device Return After Separation Deadline:

Require device return within ten business days of employment termination.

Retention and Secure Disposal Scheduling:

Define retention period for records and schedule secure data disposal after termination.

Milestones from drafting to post-termination

Sequential milestones from agreement creation through post-termination actions for a Mobile Companion Agreement and compliance tracking.

01

Drafting and Approval

Finalize terms and obtain internal approvals before distribution.

02

Execution and Signing

Collect signatures, capture audit trail, and confirm timestamps.

03

Deployment & Provisioning

Enroll device in MDM and apply security profiles.

04

Termination & Archival

Return or wipe device, archive records, and confirm disposition.

Common preparation mistakes to avoid

Failing to specify data handling rules, leaving ambiguity about encryption, backups, or permitted third-party sharing, which complicates breach response and compliance with HIPAA or state privacy laws.
Using informal or inconsistent signer names that do not match legal identities, causing tax reporting errors, authentication failures, or challenges to enforceability under ESIGN and UETA.
Skipping clear return or repair cost rules, which leads to disputes over reimbursement, insurance claims, and potential disciplinary action for employees.
Neglecting to require adequate authentication or audit trails, increasing liability and undermining the evidentiary value of electronic signatures in disputes.

Possible penalties and legal risks

Privacy Violations: HIPAA fines, state penalties.

Tax Reporting Errors: Backup withholding and IRS penalties.

Contract Disputes: Enforceability challenges in court.

Operational Delays: Procurement and support interruptions.

Insurance Claim Denials: Claims denied for noncompliance.

Disciplinary Action: Employee sanctions or termination.

eSignature vendor pricing and feature snapshot

Compare common vendor pricing and feature availability relevant to eSign workflows for Mobile Companion Agreements.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Plan	Yes, 7-day trial	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Applied examples from real organizations

Real-world examples show how Mobile Companion Agreements address security incidents, device provisioning, and HR separation procedures in varied organizations.

Optica Ventures

Optica Ventures used a Mobile Companion Agreement to formalize device support and remote management across field teams.

Enabled secure remote wipe and standardized provisioning.
The agreement reduced ambiguity about responsibility for lost or damaged devices, accelerated replacements, and provided a clear audit trail for compliance reviews and internal investigations without requiring in-person signatures. It also clarified repair cost allocation.

Fertility Centers of Illinois

Fertility Centers adopted mobile agreements to manage clinician mobile access to patient records and to meet privacy obligations across clinics.

Improved consent recording and auditability for mobile workflows.
By including HIPAA-specific provisions and a BAA, they established clear handling rules for PHI on devices, reduced risk of accidental disclosures, and simplified compliance reporting and breach notification procedures across the organization.

Frequently asked questions about execution and compliance

Answers to frequent practical questions about completing, executing, and validating Mobile Companion Agreements, including eSignature and retention concerns.

Need help? Contact support

Is an electronic signature legally enforceable?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted in most states), electronic signatures are generally valid if intent, consent, attribution, and record retention requirements are met. Certain documents remain excluded from e-signature rules.
When is notarization or witness required?
Notarization is not routinely required for device agreements, but some states or specific transaction types may require notarization or witnesses. Remote Online Notarization (RON) rules vary by state; verify with state notary commission or counsel before relying on RON.
What authentication is recommended for signers?
Use email plus an additional factor for higher-risk transactions. For sensitive data or regulatory contexts, consider SMS codes, knowledge-based authentication, or advanced signer authentication. Document the chosen method and ensure the audit trail captures IP, timestamp, and signer attribution.
Can the agreement be modified after signing?
Yes, by mutual written amendment. Amendments should be dated, signed by authorized parties, and reference the original agreement. Use an addendum or replacement agreement; maintain both original and amendment copies together for audit and legal clarity.
How should signed records be stored?
Store signed agreements in encrypted repositories with access controls, regular backups, and retention policies. Ensure the system can reproduce the record and audit trail for litigation or compliance. Follow HIPAA, IRS, or state retention rules as applicable.
What common errors invalidate agreements?
Common errors include mismatched signer names, missing dates, absent consent disclosures for consumer-facing records, incomplete authentication logs, and storing only image signatures without an audit trail. Correct errors by re-executing amended documents with proper evidence.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now