Loading published mobility-policy boundaries.
Current operations
Resolve what needs attention now
Source snapshot is read-only; assignments and notes stay in this browser.
Issue queue
Unresolved requests
| Priority | Request | Vendor | Zone | Age | Status |
|---|
Import review
Records requiring correction
Rejected records are never added to the operational queue. Only the source identifier and validation reasons are retained here.
Joined operational geography
Requests, vehicles, and watch signals
Street tiles provide geographic context. Every plotted record retains its source identifier and coordinates.
Street map unavailable
The record coordinates remain available in the Operations and Vehicle Positions views.
311 request
Veo
Spin
Cross-vendor flag
Named watch
No-park / no-ride boundary
Proactive dispatch area
GBFS fleet evidence
Vehicle positions and event-linked pile-up review
Loading the latest dated snapshot. Flags are review signals, not confirmed violations.
Coordinate view
Columbus fleet distribution
Veo Spin Cross-vendor flag Named watch
Position dots are filtered above. Red rings show clusters of at least four vehicles from more than one operator within approximately 20 metres.
Pattern detection
Explainable hotspots
Calculated from the trial issue records—not hard-coded totals.
Relative issue concentration
Longitudinal 311 evidence
Historical demand and reporting patterns
A privacy-safe extract of City records. Reporter names, contact details, and free-text descriptions are excluded.
Source boundary
Loading the historical workbook extract.
Volume over time
Requests by month
Intake channel
How requests arrived
Repeat locations
Most frequently reported addresses
Duplicate-aware review
Same-address reporting bursts
Experimental early warning
Proactive vendor dispatches
These are not 311 requests and have no SLA. They are voluntary pilot requests above current vendor requirements, intended to prevent likely future 311s in a defined place and timeframe.
Vendor accountability
Shared-mobility service levels
Official City monthly-average thresholds are shown separately from observations. Current exports cannot establish an eligible monthly vendor mean.
Verified program structure
The City evaluates Spin and Veo across 28 standards in five performance areas. Response-time standards are monthly aggregate averages: an individual duration above the target is an observation, not a standalone contractual failure. Published report cards also document event geofences and enforcement progression.
Open official SLA report cardsEvidence gap
What the public-records request would unlock
Vendor identity, assessment month, eligible-request population, notification and resolution timestamps, visual evidence review, and City inclusion/exclusion decisions are required before this application can calculate a monthly SLA result or recommend enforcement.
Open the draft records requestLearning loop
Measured outcomes
Every conclusion shows its comparison window and evidence.
Attention-first operations
Daily brief and alert subscriptions
Generated from the loaded snapshot and local workflow state. Alert delivery is a browser-local preview, not email, SMS, or production dispatch.
311-columbus-daily-forecast
Daily forecast
Checking for a published forecast…
Subscription rules
Who should be notified
Matching uses normalized severity and zone. An unchanged issue is emitted once per subscription and lifecycle state.
Deduplicated preview
Recent alert states
Local accountability
Operational activity ledger
Append-only within this browser trial. Production use still requires authenticated identities and server-enforced immutable storage.
Scheduled operations
Workflow runs
Privacy-safe product analytics
Site metrics
Aggregate audiences and behavior only. This page does not identify individual visitors.
Audience
Who is using it most
Navigation
Most-used sections
Availability
Uptime
Measurement boundary
What is verified
Read-only source artifacts