Campus Mobility: How Universities Run Bike, Scooter and Shuttle Programs

Universities run campus mobility programs by putting shared bikes, e-scooters or shuttles where students and staff need them, and deciding four things up front: who can ride, how they get access, where vehicles may go and what a ride costs. The strongest programs start small, use a private fleet for their own community, and set clear rules for speed and parking near buildings.

This guide covers the goals, the main models, access by invite or card, zones, safety, pricing, self-driving shuttles and the daily running of a campus fleet, with a planning table and questions to ask a provider.

Why do universities start campus mobility programs?

The reasons tend to fall into three groups. Write down which ones matter most on your campus, because they shape every later choice.

• Getting around a large site. Lectures, labs, halls, libraries and sports grounds can be far apart. A bike or scooter can turn a long walk between classes into a short ride, and help people who find the walk hard.
• Parking pressure. When car parks are full, shared vehicles give staff and students another way to reach the far side of campus, or to get from a car park or bus stop to their building.
• Sustainability goals. If your university has a climate or travel plan, shared bikes and electric vehicles can be part of it, as long as you measure real use rather than assume it.

Before launch, record how people move today: where the busiest walking routes are, which car parks fill first and where bikes already get parked badly. That baseline is what you will compare the program against later.

Open to the public or private for students and staff?

This is the first big decision, and it depends on who owns the roads and who you want to serve.

An open fleet

Anyone who downloads the app and signs up can ride. This suits campuses woven into a city, where visitors and neighbours pass through. It brings more riders, but also more vehicles leaving the site and less control over who is riding. An open fleet on public streets may also need approval from the city, so check that early.

A private, invite-only fleet

Only people the university invites can see and ride the vehicles. This suits campuses with private roads and paths, and programs paid for by the university as a service. It is easier to set rules, easier to explain to campus security, and simpler to fund, because every rider is a known member of the community.

Both, side by side

A campus can run a private fleet for students and staff and a separate fleet for visitors or events. Good software lets each fleet have its own prices, zones and rules. In the Axons Mobility operator console, fleets can be private and invite-only, so a free staff fleet and a paid visitor fleet can sit in the same workspace.

How do students and staff get access?

Bulk invites for a new intake

A term starts with hundreds or thousands of new people at once. Inviting them one by one is not realistic. Look for bulk invites by phone number or email, so a whole intake can be added in one step, with starting credit on each account if you want the first rides to be free. In Axons Mobility, an invite can give access to private fleets and add starting credit at the same time.

Plan the other end too. Students graduate, staff leave and exchange students go home. Ask your provider how access is removed, and set a routine for doing it at the end of each term.

Cards and tap-to-ride

Not everyone wants to use a phone for every ride, and phones run out of battery. On vehicles fitted with an NFC card reader, a rider can tap a card to start and end a ride. With Axons Mobility, a card is enrolled by tapping it on the vehicle’s reader. You can limit which vehicles a card opens, for example only the staff fleet, and there is a log of every tap. This is separate from the university’s own ID card system, so test a sample of the cards your campus already uses before promising students they will work.

How do zones keep a campus safe and tidy?

Zones are areas drawn on a map that change what a vehicle does inside them. On a campus they solve most day-to-day complaints before they start.

• Slow zones near pedestrians. Draw speed limit zones over busy walkways, squares and the areas around lecture halls at changeover times.
• No-go areas. Covered walkways, sports pitches, gardens, building interiors and places near hospitals or labs where vehicles should never be.
• Parking zones by buildings. Marked bays near entrances, bike stores and bus stops, so vehicles do not block doors, ramps or fire exits.
• A service area. The boundary of the program, so vehicles are not ridden off campus and left across town.
• Charging zones. The places where vehicles are brought to charge.

What happens inside a zone matters as much as where it is. In Axons Mobility there are five zone types (service area, no-go, speed limit, parking and charging), drawn as a polygon or a circle. Each can warn the rider, throttle the vehicle, sound an alarm and throttle, or cut motor power after a grace period, with a custom message so riders know why. A gentle warning suits a busy square; cutting power after a grace period suits a place where a vehicle must never go.

Which safety checks make sense on campus?

Students expect a quick sign-up, and campus safety teams expect evidence that risks are handled. You can meet both by choosing checks carefully.

• An ID check with a selfie confirms that the rider is the person on the account.
• A helmet photo check asks the rider to take a photo on their phone before the ride. Consider it wherever your campus rules call for helmets.
• A sobriety check, such as the 20-second check in the Axons Mobility rider app, helps stop riders who are clearly unfit from unlocking a vehicle after a night out.
• An emergency button that calls a number you set, such as campus security, and shares the rider’s live location.
• Driving score and crash detection measured by a device on the vehicle, so harsh riding and crashes at road speed are recorded.

For more detail on each check and how to add them without slowing sign-ups, read our guide to rider safety in shared mobility.

How should a campus price rides?

There is no single right answer. Choose the model that matches who pays for the program.

• Free rides. The university funds the fleet as a service. Riders never see a price, which suits staff fleets and short trips between buildings.
• Term passes and memberships. Students buy a pass for a set period. It is predictable for them and gives the program steady income.
• Pay per ride. Priced by time, distance, both, or a flat fare per trip, with a daily cap so a busy day never costs too much.
• Promos at term start. Free first rides or discounted passes during welcome week help new students try it. Give each promo a budget and an end date.

Axons Mobility supports time, distance, hybrid and flat pricing, free fleets, daily caps, passes, memberships and 11 kinds of promos, so one campus can mix models across fleets.

Can self-driving shuttles link campus buildings?

On campuses with private roads, a self-driving shuttle can run stop-to-stop between named places such as halls, the library, the sports centre and a car park. Riders pick a pickup and drop-off stop, hail a cart now or book ahead, watch it arrive on a live map and board within a set window by pressing “I’m On Board”.

The cart’s own onboard computer does the driving. The service software handles the recorded route, stops, booking, the live map, the boarding timer and fares. In Axons Mobility, the boarding timer runs on the vehicle so it keeps working where campus signal is weak, and the cart checks its route before accepting a ride, with the reason for any refusal shown to the rider. Rides can be free or a flat fare. This is a beta, so treat it as a pilot, not a finished service. Our guide to autonomous shuttle software for campuses explains the model in full.

Who runs the program day to day?

Decide early whether the university runs the fleet itself, hires a contractor or works with a student or sustainability team. Whoever it is will need to handle:

• Repairs. Punctures, brakes, lights and damage. Track each job as a work order against the vehicle and keep a stock of the parts that fail most.
• Charging. Where vehicles charge, who moves them there and when, often overnight or between peaks.
• Fleet health. Knowing which vehicles need attention first. Axons Mobility Fleet Intelligence gives each vehicle a 100-point health score.
• Reporting to the university. Agree what the program reports each term, such as rides, active riders, incidents, repairs and money, and who can see personal data. Roles and permissions let you give university staff access to what they need and nothing more.

Campus mobility planning table

What should you ask a campus mobility provider?

1. Can we run private, invite-only fleets, and invite a whole intake at once?
2. Can riders use a card as well as a phone, and how are cards enrolled?
3. What can zones do: warn, slow, sound an alarm or cut power, and can we write our own messages?
4. Which safety checks are available, and can we switch them on by time or fleet?
5. Which pricing models are supported, including free rides, passes and promos?
6. How are repairs, parts and charging tracked?
7. What reports can we give the university, and who can see personal data?
8. Where is data hosted, and how are riders’ privacy rights handled?
9. Is every feature included, or are some locked to higher plans?
10. Can we test it on our own vehicles before we sign?

Where does Axons Mobility fit?

The simplest way to test a campus plan is with a handful of vehicles on your own paths. Axons Mobility offers a free 15-day trial on your own vehicles, with every feature included. If a self-driving shuttle between buildings is on your roadmap, you can also join the self-driving shuttle beta and tell us about your campus.