Scope
Define which devices, geographic areas, facilities, and user groups the addendum controls to avoid ambiguity about applicability.
An addendum provides a precise, limited scope change that preserves the master agreement while updating operational, safety, insurance, or data-sharing terms for micromobility deployments. It reduces negotiation friction by isolating device-specific clauses and makes audits, renewals, and amendments simpler to manage.
Common signers include fleet operators, property owners, campus administrators, and municipal program managers responsible for micromobility deployments.
Legal teams and contract administrators often review the addendum for insurance, indemnity, and data-sharing clauses before signatures are finalized.
Define which devices, geographic areas, facilities, and user groups the addendum controls to avoid ambiguity about applicability.
State rider requirements, parking rules, speed limits, prohibited zones, and hours of operation so enforcement and compliance are straightforward.
Specify minimum liability and property damage limits, evidence requirements, additional insureds, and notice obligations on policy changes.
Describe indemnity, limitation of liability, and fault allocation for crashes, theft, or damage to public property.
Set terms for trip, fleet, and operational data: types shared, frequency, permitted uses, and privacy protections.
State effective period, renewal mechanics, early termination rights, and cure periods for breaches to reduce dispute escalation.
| Field | Configuration |
|---|---|
| Signature Field | Required for each party; include date. |
| Initials | Use for page-by-page acknowledgment. |
| Conditional Clauses | Show only when relevant (e.g., insurance changes). |
| Authentication | Email link, SMS code, or stronger KBA if needed. |
Confirm platform support for legal e-signatures, audit trails, and required file formats before sending the addendum.
Choose a platform that preserves tamper-evident records and audit logs, supports conditional fields, and integrates with your contract repository.
Sign within 30 days of effective date.
Provide certificate within 10 business days.
30 days to remedy most breaches.
60 days written notice typical.
Keep copies per retention schedule.
Operations and legal finalize language.
Send to authorized signers in order.
All parties sign and date.
Store executed copy and audit trail.
| Criteria | Addendum | Standalone Agreement |
|---|---|---|
| Purpose | supplement existing contract | replace or create full contract |
| Complexity | low | high |
| Negotiation Time | short | longer |
| Use Case | targeted operational updates | comprehensive commercial terms |
| 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, no card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
A university adds device parking and speed limits near dorms
A landlord permits dockless scooters with site rules
Typically signs on behalf of the operator and confirms operational compliance. The Fleet Manager certifies device maintenance schedules and executes notices for service interruptions.
Authorizes access to facilities and public easements on behalf of the owner. This signer accepts parking provisions and enforces property-specific rules under the addendum.