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
- Independent review
Independent review
Give each submitted ride revision an independent decision supported by a reason and evidence.
OverviewReview outcomes×
Bike/Scooter Sharing Platform · Independent review
New
Review outcomes
Review decisions
| Parent | Source revision | Decision | Decided at | Reason | Operation key | |
|---|---|---|---|---|---|---|
| BKN-37717 | 450 | Approve | 14 Oct | Approve rd-684 | OK-338 | |
| BKN-69593 | 900 | Return | 17 Oct | Reject rd-906 | OK-925 | |
| BKN-32162 | 560 | Approve | 18 Oct | Return rd-868 | OK-503 | |
| BKN-91315 | 240 | Return | 26 Oct | Approve rd-730 | OK-203 | |
| BKN-48885 | 60 | Approve | 08 Oct | Reject rd-103 | OK-219 |
6 of 6 records
Approve rd-684Review decisions · RD-74772
ApproveParentBKN-37717
Source revision450
Decided at14 Oct
Operation keyOK-338
What you can do
Review the ride that was submitted
Booking Supervisor decides whether the submitted ride evidence supports completion. The decision belongs to a specific revision of the booking’s ride work. It records the reviewer, decision time, reason and operation identity so the team can reconstruct what was accepted and who made that decision.
The coordinator who prepared the ride must not make its independent approval decision. A visible review queue gives staff context, while the decision procedure determines authority. Keep that separation clear during setup, especially when supervisors also help with booking preparation during a busy shift. Review is a deliberate human handoff.
How the work is organized
- Submitted scope. Booking Coordinator submits the current session after checking the vehicle, actual interval, distance and physical device evidence. Freeze the revision under review so later edits cannot silently change the basis of the decision.
- Independent decision. Booking Supervisor chooses Approve, Reject or Return and gives a reason. Approval accepts the submitted evidence; Return identifies work that needs correction before another submission.
- Execution handoff. The coordinator performs eligible approved work after review. Completion follows matching persisted effects, with the operation receipt retaining the connection between the accepted revision and the action performed.
What to agree during setup
Define what a sufficient reason looks like for each outcome. “Wrong vehicle receipt” gives the coordinator a specific correction to make; “check again” leaves the next shift guessing. Decide how the reviewer verifies provider references and who helps investigate an event that belongs to another vehicle or operating organization.
Agree how returned work becomes a corrected submission while retaining the original decision. Confirm that a reviewer cannot approve their own preparation and that the review action checks the current revision at execution time. A supervisor’s decision on an earlier version must not authorize a later edit simply because both versions share the same booking.
Check the handoff on an actual case
Use a submitted e-bike ride whose start and end times appear reasonable. Booking Supervisor notices that the return receipt refers to a different vehicle. The supervisor records Return with a reason that identifies the mismatch. Booking Coordinator finds the correct evidence and prepares a fresh submission for review.
Try editing the frozen submission and confirm that the change is refused. Have the assigned coordinator make an authorized correction through the return procedure, then submit the new revision. An attempt to review the earlier source revision should stop as stale. Review the latest submitted evidence and record a new decision. Repeat using the preparer’s own identity as reviewer and confirm that independent approval is refused. These rehearsals make the responsibility boundary visible before daily operation.
What your team sees
- Ride review inbox — Submitted ride evidence with the vehicle, revision and physical device receipt references.
- Review outcomes — Approve, Reject and Return decisions with their reason, reviewer and source revision.
Follow the work through
Use Ride review and completion for the human gate, and Cancellation and correction when accepted scope needs a controlled follow-up.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions on submitted revisions.
- Ride sessions
- Provider-confirmed ride sessions with vehicle, distance and evidence.
- Bookings
- Ride bookings with lifecycle, quoted amount and counterparty resource.
- Team members
- Operator staff linked to an organization and authenticated platform identity.
- Record attachments
- Unlock, lock and ride evidence files attached to bookings.
- Operation receipts
- Stable operation keys and result state for every guarded action.
Who uses it
Permissions- Booking Supervisor
- , Booking Coordinator and Auditor.
- The supervisor owns the independent decision; the coordinator corrects returned work and executes eligible reviewed actions.
Set up Bike/Scooter Sharing Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.