Building RoutePulse: Shuttle Operations Planning Software
RoutePulse is a shuttle operations planning platform I designed and developed to help organizations coordinate drivers, employee pickup demand, schedules, assignments, and daily transportation operations from one centralized system.
The project started from a real operational problem: transportation teams often have to make driver assignments using spreadsheets, schedules, employee demand information, and manual judgment spread across multiple systems.
I wanted to build a better way to bring that information together.
The Problem
Shuttle operations can change throughout the day.
Managers need to know:
Which drivers are available
When drivers are scheduled
When employee pickup demand is highest
Which driver should be assigned
Whether an assignment was automatically recommended or manually changed
When a driver actually begins and ends driving
How operational decisions compare with the original schedule
When this information is scattered across spreadsheets and manual processes, making quick decisions becomes difficult.
The Solution
I created RoutePulse as a centralized operations platform designed specifically around those workflows.
Instead of simply displaying schedules, RoutePulse turns operational data into information a transportation manager can actually use to make decisions.
The system combines driver scheduling, employee demand, assignment logic, schedule imports, operational tracking, and organization management within one application.
Driver Scheduling
RoutePulse provides managers with a structured view of driver availability and scheduled driving periods.
The goal is to make it easy to answer a simple operational question:
Who should be driving right now?
Managers can review scheduled drivers, make assignment decisions, and adjust operations when conditions change.
Pickup Demand Planning
One of the core features of RoutePulse is pickup-demand planning.
Employee schedule data can be used to identify periods when larger numbers of employees are expected to need transportation.
Rather than treating every 15-minute period independently, the interface is being designed to surface sustained periods of activity so managers can quickly identify meaningful demand windows.
This helps transform raw schedule data into operational guidance.
The platform can generate driver recommendations while still allowing managers to make the final decision.
Assignments can distinguish between:
Automatic recommendations
Manual assignments
Manager overrides
The system is also designed to preserve the originally suggested driver when an assignment is changed, creating better operational visibility over time.
Schedule Importing
Instead of requiring transportation teams to manually recreate employee schedules, RoutePulse includes schedule-import functionality.
Imported scheduling data is stored in the application and can be used to support pickup-demand planning and operational decisions.
Import history also provides a foundation for tracking when schedule data was uploaded and which dataset is currently being used.
Multi-Organization Architecture
RoutePulse was built as a multi-organization application rather than a single-company internal tool.
Each organization's drivers, schedules, assignments, users, and operational data are isolated from other organizations.
The platform includes organization-level access and roles for different types of users such as owners, administrators, dispatchers, drivers, and viewers.
This architecture allows the product to eventually support multiple transportation operations from the same application.
Authentication and Security
I implemented account registration, authentication, email verification, organization access controls, password recovery, and role-based authorization.
Security and organization isolation were designed as part of the core architecture rather than being added after the application was built.
Technology
RoutePulse is a full-stack application built with technologies including:
Java
Spring Boot
Spring Security
Spring Data JPA
MySQL
Flyway database migrations
HTML
CSS
JavaScript
Server-side application architecture
I also developed the underlying relational data model for organizations, users, drivers, uploaded schedules, assignments, operational activity, and related records.
From Internal Workflow to SaaS Product
A major part of this project has been turning a specific operational workflow into a reusable software product.
That required thinking beyond individual screens.
I had to consider:
Data architecture
Organization isolation
Authentication
User roles
Operational workflows
Database migrations
Schedule imports
Assignment history
Production deployment
Product positioning
UX for transportation managers
RoutePulse is currently in its demo and testing phase as I continue refining the product around real shuttle-operation workflows.
What I Built
For RoutePulse, I handled the project across product strategy, UX, application development, database architecture, security, deployment preparation, and branding.
The result is a working SaaS platform designed to turn complicated transportation data into a simpler operational decision-making system.
RoutePulse — Plan smarter. Schedule efficiently. Coordinate in real time.
RoutePulse- shuttle operations planning platform i developed to help coordinate drivers, employee pickup demand, schedules, assignments to improve operations