# Draft public-records request: shared-mobility 311 data **Proposed recipient:** City of Columbus 311 Customer Service Center and Department of Public Service, Division of Mobility & Parking Services **Subject:** Public-records request — shared electric bicycle and scooter 311 records, October 1, 2025 to present To the City of Columbus: Pursuant to Ohio Revised Code Section 149.43, I request electronic copies of the non-exempt public records described below. ## Date range and subject Please provide records created, opened, updated, or closed from **October 1, 2025 through the date the City performs its search** for 311 service requests concerning shared electric bicycles, scooters, or other shared-mobility devices. This includes records categorized as “Shared Electric Bike & Scooters” and any predecessor, successor, subtype, or substantially similar category. ## Requested 311 fields For each responsive service request, please provide the following fields when maintained: 1. Unique service-request or case identifier. 2. Date and time received, opened, assigned, first acted upon, resolved, and closed, including time zone. 3. Current and historical status, status-change timestamps, disposition, closure reason, and responsible department or workgroup. 4. Service-request type, subtype, complaint category, source description, public notes, resolution notes, and other non-exempt narrative fields. 5. Reported address, intersection, latitude, longitude, GIS identifier, neighborhood, council district, and other geographic fields. 6. Submission channel, such as web, mobile application, telephone, staff entry, or vendor referral. 7. Shared-mobility vendor or operator, vehicle identifier, and vehicle type when recorded. 8. Whether the reported condition involved an ADA or curb-ramp obstruction, travel-lane or bicycle-lane obstruction, other parking issue, tipped device, damaged or faulty device, event-related condition, or another classification used by the City. 9. Links or identifiers connecting duplicate, related, parent, child, reopened, merged, or superseded requests. 10. Vendor notification time, vendor acknowledgment time, vendor response or removal time, City verification time, and any calculated response-time or service-level result. 11. Non-exempt attachments, photographs, and attachment metadata. If providing the files themselves would materially delay production, please first provide an attachment index linked to the service-request identifier. ## Submission-pattern fields without personal information I am **not requesting names, email addresses, telephone numbers, account numbers, IP addresses, or other personally identifying information about residents**. If the system maintains a non-identifying, stable source or submitter key that can be produced without exposing identity, please include that field. A one-way hashed or otherwise pseudonymized value is acceptable. The purpose is to identify duplicate and burst submissions without identifying any person. If no such producible field exists, please provide any system-generated duplicate-detection, abuse-prevention, or linked-request indicators maintained with the records. ## Shared-mobility performance and enforcement records For the same date range, please also provide: 1. Monthly source data used to assess Service Level Agreement measures IP1 (ADA Obstruction Response), IP2 (Travel/Bike Lane Obstruction Response), and IP3 (Other Parking Issue Response) for Spin and Veo. 2. Records showing whether each responsive 311 request was included in or excluded from an SLA calculation and the reason for any exclusion. 3. Monthly numerator, denominator, response-time calculation, pass/fail result, audit sample, and supporting record identifiers for IP1, IP2, and IP3. 4. Non-exempt notices, warnings, corrective-action requests, penalties, credits, or other enforcement records tied to failures to meet those measures. 5. Data dictionaries, code lists, field definitions, business rules, and retention or deletion rules needed to interpret the produced data. 6. The underlying 311 records, timestamps, vendor-response records, and written inclusion/exclusion methodology for October 23 and October 24, 2025. The City's published October SLA report notes that each date had 16 requests submitted within one hour and that those dates were excluded from one response-time result. 7. Records documenting the creation, requested changes, operational dates, and audits of the Goodale no-parking geofence, including the September 19, 2025 audit referenced in the published SLA report cards. ## Format and production Please provide tabular data in its existing electronic form, preferably **CSV, XLSX, or JSON**, with timestamps and coordinates retained at their stored precision. If responsive information is stored across multiple tables, please provide the linking keys and a short data dictionary. Native electronic records are preferred over screenshots or PDF printouts. If the request as written is too broad or would require substantial programming, please contact me before denying it so that I may clarify or narrow the scope. The City may produce records on a rolling basis, beginning with the core 311 table and its status history. Please identify the legal basis for any redaction or withholding and produce reasonably segregable non-exempt portions. Please provide an estimate before incurring any copying or delivery charge. Thank you. ## Short portal version Please provide, in CSV/JSON/XLSX, all non-exempt City of Columbus 311 service request records concerning shared electric bikes, scooters, or other shared-mobility devices from October 1, 2025 through the date of search. Include case ID; received/opened/assigned/action/resolved/closed timestamps; full status history; type/subtype; public descriptions and resolution notes; address, latitude/longitude and geographic fields; submission channel; vendor, vehicle ID/type when recorded; obstruction classification; duplicate/related-record links; vendor notification, acknowledgment, response/removal and City verification timestamps; response-time/SLA results; and an attachment index. Also provide the monthly record-level source data and calculations used for Spin and Veo SLA measures IP1 ADA Obstruction Response, IP2 Travel/Bike Lane Obstruction Response, and IP3 Other Parking Issue Response, including inclusion/exclusion reasons, numerator/denominator, audit sample, pass/fail result, linked case IDs, and related non-exempt warnings, corrective actions or penalties. I do not request resident PII. If maintained and producible without revealing identity, include a stable pseudonymous or hashed source key solely to evaluate duplicate/burst submissions; otherwise include existing duplicate-detection or linked-request indicators. Please include data dictionaries and linking keys, produce records on a rolling basis if helpful, and contact me before denying the request as overbroad so I may narrow it.