Rider Safety in Shared Mobility: Helmet Checks, Sobriety Tests and Crash Detection

The scooter sharing rider safety features that matter most work at four moments: before the ride (ID, helmet and sobriety checks), during the ride (zones that slow the vehicle, an emergency button, location sharing), on the vehicle itself (a driving score and crash detection from a motion sensor) and after the ride (replays, risky-rider lists and hotspot maps). Together they help riders get home safely and give operators evidence they can show to cities, insurers and the public.

This guide walks through each stage, explains what to look for in software, and shows how to add checks without making the app feel slow.

Why do rider safety features matter to operators?

The first reason is simple: people can get hurt on small vehicles, and nobody running a fleet wants that. But safety also shapes the business in ways that are easy to overlook.

• City permits and tenders. When a city decides who may operate, it will often ask how you handle speeding, parking, impaired riders and incidents. “We ask riders to be careful” is a weak answer. A list of checks you actually run, with records behind them, is a strong one.
• Insurance conversations. Insurers treat what they cannot see as risk. If you can show how riders are verified, how speed is limited in busy areas and how incidents are recorded, you have something concrete to discuss.
• Reputation. One bad incident travels fast. Visible safety steps, such as a helmet check or a slow zone near a school, tell riders and residents that the service is run with care.
• Cost. Crashes damage vehicles, create support work and can lead to claims. Spotting risky habits early is cheaper than dealing with the result.

None of this needs big promises. It needs features that work every day, and records that show they did.

What safety checks should happen before the ride?

Checks before unlock are the only ones that can stop a risky trip from starting. The trick is to make them quick enough that honest riders barely notice them.

ID check with a selfie

An identity check confirms the rider is a real, eligible person. That helps with age limits and with accountability if something goes wrong. A good flow asks for an ID document and a selfie and matches the two. In the Axons Mobility rider app this takes about a minute, and riders only do it once.

Helmet photo check

Where helmets are required or encouraged, the app can ask for a photo of the rider wearing one before unlocking. Privacy matters here. In Axons Mobility the helmet check runs on the phone itself, and the picture never leaves the phone. Riders tend to be more comfortable taking a photo when they know it is not being uploaded anywhere.

Sobriety and reaction test with a cooldown

Late-night rides carry extra risk. A short test on the phone can catch a rider who is clearly not fit to ride. The Axons Mobility sobriety check uses a 20-second reaction test, a trace-the-line test and a hold-steady test. If a rider fails, a cooldown starts, and the operator decides how long it lasts.

A cooldown is fairer than a permanent block, because a rider who was simply tired can try again later. It still stops someone from retrying straight away until they pass by luck. You also do not have to switch on every check everywhere. You might use the sobriety test only late at night, or the helmet check only on faster vehicles. The right mix depends on local rules and your riders.

How can software keep riders safe during the ride?

Once the vehicle is moving, safety comes from the connected vehicle and the map.

Zones that slow the vehicle or cut power

Zones are areas drawn on the map with a rule attached. Axons Mobility has five types: service area, no-go, speed limit, parking and charging. For each zone you choose what happens when a rider breaks the rule: a warning, a lower speed, an alarm plus a lower speed, or cutting motor power after a grace period.

The grace period matters. Cutting power the instant a rider crosses a line could stop them in the middle of a road. A short warning first gives them time to slow down or leave the zone safely. Custom messages help too. “Pedestrian area ahead, speed limited” is clearer than a generic alert, and riders who understand why a rule exists are more likely to follow it.

Speed-limit zones and slow-zone banners

Speed-limit zones suit busy squares, waterfronts, campuses and streets around schools. On the rider’s live ride screen, a slow-zone banner appears when a limit applies, so a vehicle that suddenly slows down does not feel like a fault.

Emergency button with live location

If something goes wrong, the rider needs help without digging through menus. The Axons Mobility emergency button calls a number the operator sets (112 by default) and streams the rider’s live location to the operator, so your team knows exactly where to send help.

Sharing location with a friend

Riders can share their live location with a contact for 15 minutes, 1 hour or 8 hours. It is a small feature, but it means a lot to someone riding home alone at night. The app also keeps recording the ride when the mobile signal drops, so the trip record stays complete.

Why measure riding on the vehicle instead of the phone?

Many apps estimate riding behaviour from phone sensors. In shared mobility that approach has real limits:

• The phone may sit in a pocket, a bag or a hand, moving separately from the vehicle.
• Phone models measure differently, so the same ride can produce different readings.
• Phones often restrict sensors running in the background to save battery.

A motion sensor fixed to the vehicle avoids all three problems. The Axons Mobility connected device reads motion 100 times a second and recognises harsh braking, sharp corners, swerves, speeding, potholes, tilt, towing and crashes. Because every vehicle carries the same hardware, driving scores can be compared fairly across riders and across the fleet.

Crash detection without false alarms

A scooter hitting a pothole or being knocked over at the kerb creates a sharp jolt, much like a real impact. If every jolt counted as a crash, your team would soon start ignoring the alerts. Axons Mobility only treats an impact as a crash when the vehicle was moving at road speed, and potholes are recorded as their own events. Fewer false alarms means the real ones get attention.

What should operators do with safety data after the ride?

Data only helps if someone acts on it. After the ride, the useful tools are the ones that turn events into decisions.

• Ride Replay. Riders can replay their own ride and zoom into moments of harsh braking, speeding or zone breaches. Seeing exactly where it happened teaches more than a number. Operators see each trip in the trips inspector, with an event timeline and a driving score.
• Riskiest riders. A list of the riders with the most risky events shows who needs a nudge. Compare events against distance, not raw counts, so a rider who simply rides a lot does not look dangerous. The Axons Mobility Safety page shows harsh events per 100 km, which makes that comparison easy.
• Hotspot maps. When many different riders brake hard at the same corner, the problem is probably the road: a blind junction or a broken surface. When one rider brakes hard everywhere, the problem is the rider. The Axons Mobility hotspot map separates the two, so you can raise a road issue with the city or talk to the rider instead of guessing.
• Safety tips and temporary speed caps. With Rider Intelligence you can send safety tips to a group of riders at once, or set a temporary speed cap for riders with low safety scores. A temporary cap lowers risk without banning a paying customer.

All of this sits in the operator console, next to the live map and the support desk, so safety is part of daily work rather than a report nobody opens.

Rider safety features by stage

How do you add safety checks without losing riders?

Every extra step before unlock is a chance for a rider to give up. These habits keep checks from hurting sign-ups:

1. Explain why. One line, such as “Helmet check required in this area”, turns a hurdle into a reason. Custom zone messages do the same job during the ride.
2. Keep each check fast. A one-time ID check of about a minute, a quick helmet photo and a short reaction test feel reasonable. Long forms and waiting screens do not.
3. Show all the steps at once. Few things annoy a rider more than finishing one step and finding another. The Axons Mobility “Before You Ride” sheet lists every remaining step together, so riders know exactly what is left.
4. Start where the risk is. Switch checks on for certain hours, areas or vehicle types first, look at the results, then widen them.
5. Be fair about failures. Use cooldowns rather than bans for a failed test, and speed caps rather than blocks for low scores.
6. Be open about privacy. Say plainly what is stored and where. A helmet photo that stays on the phone is an easy point to make. The security page has the details.

If you want to see these safety features working on your own fleet, the free 15-day trial runs on your own vehicles, with the rider app, the operator console and the Safety page ready to use.