How to Run a Campus Safe-Ride Program or On-Demand Campus Shuttle

Late-night safe-ride programs give students, staff, and visitors a way to get home or to their car without walking alone after dark. Many started as a phone number and a van. As a campus grows, the phone queue gets longer, and the program has little data to show for its budget. This guide covers how to plan an on-demand campus shuttle or safe-ride program, from the service area to the numbers you should report.

The details depend on your campus, your security department, and your institution's policies. Involve campus safety, transportation, risk management, and legal counsel from the start.

Service area and hours

Draw the service area first. Many programs cover the campus plus the nearby neighborhoods where students live, bounded by how far a vehicle can travel and return in a reasonable time. Be explicit about the edges. A rider just outside the line who is refused at 1 a.m. becomes a complaint.

Then list the stops riders use most: residence halls, libraries, labs, parking lots and garages, the student center, transit stops, and athletic facilities. Named stops make requesting faster and pickups more accurate than typed addresses.

Set hours around real need. Safe-ride demand tends to build as libraries and evening classes let out and after events. If you're unsure, start with a wider window and trim it once you have data.

Eligibility

Decide who can ride:

• Students only, or also staff, faculty, and visitors?

• Does a rider need to sign up with a campus email address or ID?

• Can riders bring a friend, and how many people can ride together?

• Are trips limited to the service area, or can they run from campus to a nearby address?

• Is there a limit on rides per night, so the service doesn't become a general taxi?

Write the rules down and publish them in the app and on your website, so drivers aren't making judgment calls at the curb.

Safety features riders and parents expect

A safe-ride program is judged on safety first. Look for these, whatever software you use:

• Driver verification. Identity and license checks for every driver, background checks as your policy requires, and reminders before documents expire.

• Trip PIN. A short code the rider gives the driver before the trip starts, so nobody gets into the wrong vehicle.

• Share my trip. A live link a rider can send to a friend or roommate, showing the driver, vehicle, and route, which expires after the trip.

• SOS button. In both the rider and driver apps, calling emergency services and alerting your team with the trip location. Agree with campus police or security on who receives the alert and what they do next.

• Driver and vehicle details before pickup. The driver's photo, the vehicle, its plate or number, and its live position, so riders can confirm before they get in.

• Masked contact. Riders and drivers can chat or call without seeing each other's phone numbers.

• Trip records. Who rode, with which driver, when, and along which route, for incident reviews.

Decide in advance how you'll handle an incident report: who investigates, how you pull the trip record, and how you follow up with the rider. Treat trip records as sensitive, and follow your institution's privacy policies on who can see them and for how long.

Plan how you'll serve riders with disabilities, including riders who use mobility devices. Work with your disability services office before launch.

Staffing

Programs generally use student drivers, staff drivers, or a contracted operator.

• Student drivers know the campus and can work evening shifts around classes, but they need training, supervision, and cover during exams and breaks.

• Staff drivers bring consistency and are easier to supervise, but late-night shifts can be harder to fill.

• A contracted operator brings drivers and vehicles. You set the service rules, and your contract should keep your access to trip data.

Whichever model you choose, check driver license and driving-record requirements with your insurer and risk office, train drivers on the service area and incident procedures, and limit the hours a driver can stay online in a shift.

Plan staffing by the hour. As a hypothetical example, one driver at 9 p.m. and three at midnight may serve riders better than two all night. The only way to know is to measure.

Free or paid

• Free rides are paid for by student fees, a department, or a parking and transportation budget. Free rides remove a barrier for the riders who most need the service, and trip data still shows what the program delivers.

• Flat fares charge a small fixed amount per ride, which can discourage using the service for short daytime hops.

• Distance-based fares suit programs that also cover longer off-campus trips.

• A mix by area keeps rides free inside the core campus and charges a fare for trips to farther neighborhoods.

If rides are free, decide how you'll prevent misuse without adding friction for legitimate riders. Eligibility checks at sign-up and limits on destinations are often simpler than rules applied to every ride.

Measuring demand

A safe-ride program has to justify its budget each year. Collect these numbers from the first night:

• Requests and completed trips by hour and day of the week

• Completion rate: the share of requests that became trips

• Time to match and pickup time

• Requests no driver accepted, and when they happened

• Cancellations by riders and by drivers

• The most-used pickup points and destinations

• Driver hours online compared with hours spent on trips

Read them together. Low completion late on Thursday nights means you need another driver then. Long pickup times with enough drivers online mean drivers are waiting in the wrong places. Rider cancellations after long waits mean riders are giving up, and some may be walking instead, which is the outcome the program exists to prevent.

Share a short report each term with campus safety, student government, and whoever funds the program: trips delivered, typical waits, and the changes you made.

A launch checklist

• Service area, stops, and hours defined

• Eligibility rules written and published

• Safety features chosen, and the SOS response agreed with campus police or security

• Driver model chosen, and drivers checked and trained

• Insurance and risk review complete

• Fare model decided: free, flat, distance-based, or a mix by area

• Reporting set up before the first night

• A pilot of a few weeks, followed by a review

How Levy fits

Levy's campus shuttle and safe-ride software supports this kind of program. Students request from an app under your program's brand, choose named stops, and see their driver's photo, vehicle, and live position as it arrives. A trip PIN, share-my-trip links, an SOS button in both apps that dials the local emergency number and alerts your team, masked chat and calling, and driver identity and license checks with background-check support in the US are built in.

You control who can sign up and where the service runs, choose free, flat, or distance-based fares for each service area, and get reports on trips, completion rate, time to match, and cancellations, with a timestamped timeline for every trip. Drivers use the Levy Driver app and join your program with an invite code, and your team approves each one.

Levy provides the software. Your institution or its operator runs the service and holds the licenses and insurance it needs. For pickup points and wait-time targets on daytime shuttles, see our guide to on-demand shuttles for resorts and communities, or book a demo to walk through your program.