Routes, trips and boarding — one traceable flow.
Whether you run a school shuttle, a staff bus or a delivery round, the work underneath is the same: a fixed sequence of stops, a vehicle and driver assigned to each trip, and a list of who should board where. What goes wrong is also the same — assignments live in a spreadsheet, drivers get their instructions by chat, and nobody knows at the end of the day whether every stop was actually served. Tenderely BPM ties the route, the trip and the boarding record into one place, without code, and keeps it accessible on the road.
What does a transport operation repeat every day?
01
Defining and updating routes
A route is an ordered list of stops. Stops get added, removed or resequenced when demand changes, and every vehicle and driver on that route needs to know immediately.
02
Assigning a vehicle and driver to a trip
Each departure needs a vehicle that is available and a licensed driver who is on duty. When either is missing, the trip does not go — or goes without a record.
03
Communicating the manifest to the driver
The driver needs to know who to pick up, in which order and at which stop. A printed sheet from yesterday, or a chat message, is how this usually travels.
04
Recording boarding and alighting
Who actually got on, who was absent and who was dropped at an unexpected stop — without a record at the point of boarding, this information is gone by the time anyone asks.
05
Handling exceptions mid-trip
A passenger cancels at the last minute, a stop is unreachable, a vehicle breaks down. Someone needs to decide, and that decision needs to reach the driver before the bus does.
06
Reviewing trip history and compliance
Did all passengers travel on the days they were supposed to? Were all stops served? This question comes from parents, HR teams, clients and auditors alike.
Where does this break down today?
Assignments live in a shared file
Vehicle and driver assignments sit in a spreadsheet that everyone edits. By morning, two drivers have the same bus or the file has simply not been updated.
Drivers work from chat messages
The day's manifest arrives via a messaging app. The driver scrolls back through the thread to find it, the coordinator has no confirmation it was read, and updates after sending are invisible.
Boarding is not recorded at all
When attendance is taken on paper or not at all, there is no answer to whether a passenger was served — only the driver's recollection, which is not audit-proof.
Exceptions have no trail
When a stop is skipped or a passenger is swapped, the decision is made by phone. No record means no way to explain it later, and patterns of problems stay invisible.
What changes with Tenderely BPM
01
The route is a structured record
Stops, their order, times and any special notes all live in one place. When a stop changes, the update is part of the record, not a correction sent to a chat group.
02
Trips go through an assignment step
Vehicle and driver are confirmed before the trip opens. Conditional steps can require a supervisor's approval for a substitution, so the exception is recorded, not just acted on.
03
The driver works from a mobile app
The day's trips and their manifests are accessible in the iOS and Android apps. The driver sees their stops, marks boarding and flags exceptions from the same screen, on the road.
04
Boarding is recorded at the point it happens
Present, absent, boarded at a different stop — the driver logs it on the spot. The record is timestamped and tied to the trip, not reconstructed from memory.
05
Exceptions follow an approval step
A route deviation or passenger swap can be routed to a coordinator for approval before it is confirmed. SLA reminders mean the coordinator is notified without the driver having to call twice.
06
Trip history is a dashboard, not a file
Tenderely BPM gives you completed trips, boarding rates, absent passengers and late departures as live data. Compliance questions get answered from a screen instead of from a folder.
FAQ
Does it work for school shuttles, staff buses and delivery rounds at the same time?
+
Yes. The underlying structure — ordered stops, a vehicle and driver bound to a trip, and a boarding or delivery record — is the same for all three. You configure the forms and steps to match each operation, and role-based access keeps school routes and delivery rounds separate for the people who manage them.
Can parents or staff members see their own trip assignments from outside?
+
Yes. A public form can be used to let external users submit requests or view status updates. For regular passengers, a linked external user account limits visibility to their own record — they see their stop, their schedule and any change that affects them, but nothing else.
What happens when a vehicle breaks down or a driver is suddenly unavailable?
+
An exception record opens in the same flow. The coordinator is notified, the substitution goes through whatever approval step you have configured, and the original trip record captures what actually happened. The audit history keeps the original plan and the exception side by side.
Can we report on which passengers travelled on which days?
+
Yes. Because each boarding event is a structured record tied to a passenger, a trip and a date, you can filter and report on any combination — attendance by passenger, trips by route, exceptions by driver. Reports can be exported to Excel or CSV.
How long does it take to get a working setup?
+
The Routes and Transport package starts with forms, workflows and a dashboard already in place. You adjust the stops, roles and approval steps to match your operation and publish. Most teams have a working flow on the same day they start, without writing any code.