These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Bike/Scooter Sharing Platform
- Features
- Ride sessions
Ride sessions
Record actual ride timing, distance and device evidence before submitting the ride for review.
OverviewRide review inbox×
Bike/Scooter Sharing Platform · Ride sessions
New
Ride review inbox
Approval conditions
| Parent | Vehicle | Status | Revision | Started at | Ended at | |
|---|---|---|---|---|---|---|
| BKN-74297 | RSR-3393 | Submitted | 500 | 23 Oct | 26 Oct | |
| BKN-82711 | RSR-9532 | Submitted | 890 | 17 Oct | 23 Oct | |
| BKN-67641 | RSR-1485 | Submitted | 280 | 21 Oct | 26 Oct | |
| BKN-82353 | RSR-6726 | Submitted | 160 | 21 Oct | 27 Oct | |
| BKN-76052 | RSR-1932 | Submitted | 850 | 20 Oct | 22 Oct |
6 of 6 records
URI-954Ride sessions · RS-59038
SubmittedParentBKN-74297
VehicleRSR-3393
Revision500
Started at23 Oct
Ended at26 Oct
What you can do
Build the ride record from actual service
A reservation describes an intended interval. The ride session describes the service that occurred. Booking Coordinator connects the session to its booking and organization, selects the actual vehicle and records the observed start, end and distance. The session also carries the ride fare and references to device receipts for vehicle release and return.
Keep scheduled and actual times distinct. A customer may arrive late or finish earlier than expected. The recorded ride should explain those facts to Booking Supervisor without rewriting the original booking as if the plan had always matched the outcome. The provider’s device evidence supports the physical handoff at each end.
How the work is organized
- Start of service. Booking Coordinator checks the selected vehicle and actual arrival before moving the ride into progress. Obtain the device receipt through the configured provider connection and keep its time alongside the ride start.
- End of service. Record actual end time, distance and the provider’s return receipt. Check that the event belongs to the same vehicle and booking before treating the ride as ready for submission.
- Submission. Submit the completed evidence for the current revision. Booking Supervisor reviews that fixed submission independently; changing the underlying ride requires a fresh review of the corrected scope.
What to agree during setup
Agree how vehicle release and return events arrive from your device provider. Establish which provider reference identifies a physical event and how staff handle delayed receipts. A successful request to a device service must be followed through to the actual event evidence before the ride is presented as complete.
Choose who supplies distance and fare values and how staff check them against provider records. Use the same vehicle identity throughout the booking and session. Retain legacy vehicle wording as historical context while using the selected vehicle record for new operating decisions. Agree how staff reconcile a device timestamp with the organization’s working time zone.
Check the handoff on an actual case
Rehearse a scooter ride that starts at 09:05 and ends at 09:32. Booking Coordinator records the actual interval, the reported distance and the selected scooter. The provider confirms vehicle release immediately but sends the return receipt later. Keep the ride evidence open for follow-up until both physical events can be traced.
When the return receipt arrives, check its vehicle and time before submitting. Booking Supervisor compares the session with its attachments and provider references. If the distance belongs to another ride, return the submission for correction. A new revision must preserve the earlier evidence and receive its own decision before completion. Repeat the exercise with an end time earlier than the start to confirm that inconsistent evidence stops the handoff.
What your team sees
- Ride progress board — Sessions moving through Draft, In Progress and Ended, with their vehicle and revision.
- Completed rides — Completed service with actual timing, distance and recorded fare.
- Ride review inbox — Submitted sessions ready for an independent evidence decision.
Follow the work through
Follow Ride review and completion, then use Reconciliation and payment to inspect uncertain effects and provider payment events.
What it keeps track of
Data model- Ride sessions
- Provider-confirmed ride sessions with vehicle, distance and evidence.
- Bookings
- Ride bookings with lifecycle, quoted amount and counterparty resource.
- Resources
- Bikes, scooters and docks available for sharing operations.
- Record attachments
- Unlock, lock and ride evidence files attached to bookings.
- Review decisions
- Independent reviewer decisions on submitted revisions.
- Operation receipts
- Stable operation keys and result state for every guarded action.
Who uses it
Permissions- Booking Coordinator
- , Booking Supervisor, Fleet Technician and Auditor.
- The coordinator prepares the service evidence; the supervisor makes the independent review decision.
Set up Bike/Scooter Sharing Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.