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
- Reservations and capacity
Reservations and capacity
Reserve an eligible interval and keep the selected resource tied to the booking decision.
OverviewMy bookings×
Bike/Scooter Sharing Platform · Reservations and capacity
New
My bookings
Bookings
| Record number | Subject | Status | Starts at | Ends at | Resource | |
|---|---|---|---|---|---|---|
| BKN-76012 | Requested bkn-958 | Requested | 27 Oct | 01 Nov | RSR-4466 | |
| BKN-28110 | Held bkn-334 | Held | 16 Oct | 18 Oct | RSR-4179 | |
| BKN-11418 | Confirmed bkn-746 | Confirmed | 26 Oct | 02 Nov | RSR-5945 | |
| BKN-71148 | In Progress bkn-410 | In Progress | 11 Oct | 16 Oct | RSR-5415 | |
| BKN-55586 | Completed bkn-753 | Completed | 04 Oct | 07 Oct | RSR-4962 |
6 of 6 records
Requested bkn-958Bookings · BKN-76012
RequestedStarts at27 Oct
Ends at01 Nov
ResourceRSR-4466
Revision860
What you can do
Make the reservation explainable
Booking Coordinator starts with the requested ride, customer name, selected resource and intended start and end. The booking holds its lifecycle and quoted amount. Its resource lines preserve reserved units and the capacity used for the interval check, together with setup and cleanup minutes. Those details explain why an apparently open slot may already be occupied.
Requested, Held and Confirmed describe successive commitments. The coordinator checks entitlement and an eligible interval before placing a hold, then checks the required consent and deposit evidence before confirmation. Define those operating rules during setup so staff know what evidence is sufficient and what must wait for follow-up.
How the work is organized
- Request ownership. Every booking identifies its organization and assigned team member. Booking Coordinator uses that ownership to prepare the request and to keep the next shift informed when the customer has not yet met confirmation conditions.
- Capacity claims. Resource lines connect the booking to the selected resources and carry the reservation quantities. Include setup and cleanup windows in the interval check and make hold expiration release the reservation only once.
- Confirmation. Booking Coordinator requests the move from Held to Confirmed. The confirmation action checks verified provider evidence when a deposit is required. Booking Supervisor investigates payment discrepancies. Preserve the quote as the commercial expectation.
What to agree during setup
Choose hold duration, capacity rules and the treatment of adjacent intervals. Decide whether a customer request can occupy a vehicle while staff are collecting required consent, and what happens when that collection takes longer than the hold. Identify the source of customer entitlement and arrange the connection or staff procedure that checks it.
Agree how the operating time zone applies to customer-facing times. A start time entered for the wrong organization can make an otherwise sensible reservation collide with another booking. Also decide how coordinators pass a booking to another owner without losing responsibility for its unresolved conditions.
Check the handoff on an actual case
Use a bike requested for a ride ending just before the next reservation begins. Add the cleanup interval used by your operation. Booking Coordinator compares both bookings and discovers that the cleanup window overlaps the next claim. The coordinator offers another eligible interval or resource before asking for confirmation.
Next, let the first hold expire while a confirmation attempt is waiting. Rehearse the outcome with the Booking Supervisor: the old hold must not claim capacity again, and a repeated expiration must not release an unrelated reservation. The operation evidence should identify the booking and revision that were checked. Finally, verify that a quoted amount with no verified deposit evidence cannot satisfy a deposit requirement.
What your team sees
- Reservations queue — Requested, Held and Confirmed bookings with their owner, resource and quoted amount.
- My bookings — The assigned coordinator’s booking work and current revision.
- Booking schedule — Confirmed and active ride intervals with their scheduled start and end.
Follow the work through
Use Reserve and confirm for the full reservation handoff and Cancellation and correction for an eligible release of capacity.
What it keeps track of
Data model- Bookings
- Ride bookings with lifecycle, quoted amount and counterparty resource.
- Booking resources
- Reserved resource lines attached to a booking.
- Resources
- Bikes, scooters and docks available for sharing operations.
- Organizations
- Sharing operator organizations with time zone and currency scope.
- Team members
- Operator staff linked to an organization and authenticated platform identity.
- Payment evidence
- Provider payment authorization, capture, refund and void evidence.
- Operation receipts
- Stable operation keys and result state for every guarded action.
Who uses it
Permissions- Booking Coordinator
- , Booking Supervisor and Auditor.
- The coordinator prepares and performs eligible booking actions; the supervisor examines disputed reservations and supporting evidence.
Set up Bike/Scooter Sharing Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.