Rider booking and confirmation
Design a short reservation flow with departure reference, stop label and separate requested, confirmed and changed states. Keep the trip summary legible on common phones.
Give riders a clear confirmation for their actual departure and help the boarding team see which reservations changed. Start with one route and a realistic vehicle swap.
See the seat change example
01 / What we build
Design a short reservation flow with departure reference, stop label and separate requested, confirmed and changed states. Keep the trip summary legible on common phones.
Show how many reservations a smaller vehicle affects. Give the operator a review step before sending replacement-trip offers or marking riders for follow-up.
Build a list with the last refresh clearly shown, then test how staff reconcile a changed departure when a phone displays an earlier booking confirmation.
City context, honestly stated
Electronics City Industrial Township Authority describes shuttle services serving workplaces in Electronics City, Bengaluru. The example is an independent fictional employer route, separate from the authority’s service. GreyBath delivers mobile app work remotely.
On a fictional 6:20 p.m. staff departure, 19 people reserve seats. The dispatch team replaces a 24-seat vehicle with a 16-seat vehicle. Keep 16 confirmed reservations and identify the three affected riders using the operator’s agreed allocation rule. The rider screen should say whether the first departure is still confirmed.
The later departure has two spare places. Offer them to two of the three affected riders. Track each offer separately until accepted. The third rider stays in the coordinator’s follow-up list and does not receive a false confirmation.
Give the boarding team the current departure and a list that marks moved riders. If a rider shows an older confirmation on the phone, staff can compare its departure reference with the current list and explain the next action.
Where it fits
Invite one rider, one boarding team member and the person who can change a trip. Ask each to explain what a confirmed seat looks like.
Set the capacity rules and decide which departures may be combined. See who still needs a phone call or message.
Book a seat, check the departure and accept a different trip when one is offered.
Check the current departure list and flag a rider who presents an earlier confirmation.
Set which staff can see identifiers or edit a trip, and decide what data the pilot needs to retain.
How we work
Load 19 reservations on the first departure and two spare places on the second. Ask staff to find both counts and identify the named stops.
Switch the first trip to 16 seats. Confirm 16 ordinary reservations, two offers for the later trip and one follow-up for the coordinator.
Have a rider accept an offer while a second rider keeps an older confirmation. Verify the current list for each departure and hand off any unresolved reservation.
Use one employer route, the staff devices already in use and the operator’s reservation policy. Keep decisions about capacity and trip changes with the operator.
Discuss your projectCheck that two similar stop names can be distinguished and that specific departures keep stable references when vehicle assignments change.
Record who allocates seats, who can offer an alternative and what happens when an offer expires or is declined.
Decide which details riders and boarding staff need to see. Label an older list so staff know which decisions need a current lookup.
A first pilot can use a reservation, a departure reference and dispatch updates. Add live positions if the operator can supply reliable data and the design makes clear when it was updated.
Give staff a stable reference to look up in the current list. Show the departure and refresh status on both sides so the change can be explained.
Review a redacted export and how it identifies riders, stops and departures. If it has stable identifiers, test a small import before designing a live connection.
The operator sets the allocation rule and the review roles. The app shows who was affected and tracks the offers made.
Bring one synthetic trip sheet, a common vehicle-change scenario and the current rider message for a replaced departure.
Bring one cancelled or combined trip