A rented e-scooter crash may leave records in a rider account, mobile application, payment system, customer-support platform, device-management system, maintenance file, and the physical scooter itself. A receipt or route screenshot can help identify a trip, but it may omit device status, time settings, event details, support contacts, later corrections, or the method used to create the display.

A scooter trip record should connect the rider account, reservation, device identifier, ride interval, route or event data, charges, reported problem, device condition, and export history without assuming that any one field proves how the crash occurred.

Address safety and medical needs before handling devices

Emergency care and scene safety come before record collection. A damaged scooter or battery can also present physical and fire concerns. The U.S. Consumer Product Safety Commission’s micromobility information center identifies brakes, throttle, handlebars, lights, tires, cables, frame, battery, and charger among items relevant to safe device condition. Follow emergency, fire, law-enforcement, operator, manufacturer, and treating-provider instructions rather than powering, charging, moving, or testing a damaged device merely to gather evidence.

Identify the exact account, trip, and scooter

  • Rider name and account identifier, contact information used, application name and version, operating system, device, login method, and account-status date
  • Reservation or ride ID, unlock method, start and end times, displayed route, start and end locations, pauses, charges, discount, receipt, and payment source
  • Scooter fleet number, QR code, serial number, model, color, physical label, photograph, operator, and final location
  • Whether the ride was rented, personally owned, borrowed, employer-provided, or part of another arrangement verified before requesting the wrong record set

Preserve what the rider can see without changing the account

  • Complete screenshots or screen recording showing application name, account, trip list, ride detail, timestamps, route, charge, and surrounding context
  • Native account download or privacy export when the operator supplies one, with the request, date range, file names, format, instructions, and delivery message
  • Receipt email, text message, push notification, in-app message, support ticket, photograph, video, and attached file retained in original form
  • No account deletion, trip editing, repeated device pairing, software update, or destructive troubleshooting performed solely for documentation

Request operator-held records by category, not guesswork

  • Trip and reservation data, account records, payment and refund history, support contacts, incident report, complaint, and internal reference number
  • Scooter assignment, deployment, retrieval, inspection, battery, repair, maintenance, prior complaint, fault code, status change, and removal from service
  • Location, speed, acceleration, braking, orientation, unlock, lock, communication, or other device data only if that system actually records it
  • Data dictionary, field definitions, time zone, clock source, precision, retention period, export method, filters, omitted fields, and person or system producing the file

Not every operator records every category, and a displayed route may be estimated or simplified. An unavailable field should be marked unavailable or unknown, not called zero. A preservation request should identify the account, trip, device, place, time range, and record categories without claiming that a system contains information that has not been confirmed.

Understand formal production tools without overstating access

North Carolina Rule of Civil Procedure 34 addresses production of electronically stored information and tangible things from parties in a civil action. Rule 45 addresses subpoenas, including production from nonparties under its terms. These rules do not make every private platform record available on informal request. Applicable procedure, privacy, scope, objections, custody, and court supervision require matter-specific review.

Preserve the physical scooter and custody history

  • Wide and close photographs of the complete device, identifiers, controls, display, brakes, tires, handlebars, stem, deck, lights, battery area, damage, debris, and final position
  • Person or company collecting, moving, storing, charging, inspecting, repairing, testing, returning, redeploying, or disposing of the scooter and each date
  • Operator inspection, insurer inspection, law-enforcement custody, repair report, parts replacement, destructive testing, and condition change kept as separate events
  • No appearance, fault code, route point, or damage mark treated as a technical-causation conclusion without an appropriate foundation

Keep native files, provenance, and a traceable summary

North Carolina Rule of Evidence 901 addresses authentication and identification. Retain the original file, producing person or system, device, account, export instructions, metadata, hash when available, transfer, storage, and each transformed working copy.

Rule 1006 addresses summaries of voluminous writings, recordings, or photographs under its conditions. A trip chronology can organize many records, but each row should trace to an underlying source, and the original materials should remain available.

  • Source ID, field or record, raw value, displayed value, time zone, interpretation limit, and linked original
  • Agreement, conflict, gap, correction, duplicate, estimated value, or unknown status recorded
  • Rider report, operator record, device output, witness observation, photograph, and technical opinion kept in separate columns
  • Crash mechanism, product condition, rider conduct, medical causation, and legal responsibility treated as separate questions

The related guide to reading imaging and clinical findings after a scooter-related head injury covers the medical record. This page owns the rental account, trip, platform, and device evidence.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about Charlotte traumatic-brain-injury claims involving scooter crashes and digital records. Medical care, lawful access, preservation, technical interpretation, and legal responsibility depend on the actual circumstances and qualified review.

Sources