Scope of Services
Describe exactly what services are provided, where, and under what operational conditions; include uptime targets, maintenance obligations, and escalation procedures to reduce ambiguity and dispute risk.
A well-drafted agreement clarifies responsibilities, reduces disputes over charging access, sets measurable service levels, protects customer data, and preserves enforceability when executed electronically under ESIGN and state e-signature laws.
Organizations and individuals across fleet, infrastructure, and mobility services rely on a standard agreement to align operational and legal expectations.
The document is suitable for suppliers, operators, fleet owners, and facility hosts who need a formal, legally binding record of the relationship.
Fleet Manager — Individual or corporate officer authorized to bind the fleet owner for procurement, billing, and operational commitments including acceptance of service levels and indemnity clauses.
Charging Operator — Contracting party who installs, operates, and maintains charging infrastructure and who is authorized to accept operational terms, data access permissions, and payment settlements on behalf of the provider.
Describe exactly what services are provided, where, and under what operational conditions; include uptime targets, maintenance obligations, and escalation procedures to reduce ambiguity and dispute risk.
Define measurable SLAs for station availability, response and repair times, and acceptable downtime thresholds; link remedies, credits, or termination triggers to SLA breaches.
Specify pricing units (per kWh, per session, subscription), invoicing cadence, dispute procedures, and late payment remedies to ensure predictable revenue and reconciliation.
Set data ownership, permitted uses, retention, and security obligations including encryption, access controls, and breach notification responsibilities to satisfy privacy and compliance demands.
Allocate responsibility for property damage, personal injury, data breaches, and third-party claims; consider caps, carve-outs, and insurance requirements for clarity.
State effective date, contract length, renewal terms, early termination rights for cause, and post-termination data return or deletion processes to prevent disputes.
| Field | Configuration |
|---|---|
| Authentication Method | Email link, SMS code, or stronger KBA as needed |
| Signature Fields | Place signature, initials, dates, and typed-name fields |
| Conditional Clauses | Show or hide exhibits based on selections |
| Notifications | Set reminders and completion alerts for signers |
Select a signing platform that supports your authentication and retention needs, integrates with existing systems, and provides an auditable trail.
Date contract starts; use MM/DD/YYYY for clarity
Operational start tied to installation or acceptance tests
Specify monthly, quarterly, or per-event billing cadence
Termination or change notices typically 30–90 days as agreed
State automatic renewal terms and opt-out deadlines
Final commercial terms agreed and redlines cleared
Document is signed electronically and audit trail saved
Hardware installed, tested, and accepted per acceptance criteria
Services begin and billing activates per contract schedule
| 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 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 |