You can now review, correct and approve carpool and vanpool trips that failed automatic validation, directly from the Management Dashboard. You can also edit users' trips retroactively.
Things happen. A phone battery dies mid-trip, or a partner forgets to start recording. Instead of contacting CommuteHub Support and going back and forth, users can request a manual review right in the app. The request lands in your Trips list with the reason the recording failed, the user's explanation and their proposed corrections, so you can decide in a few clicks.
How a request reaches you
Users can request a review for any eligible carpool or vanpool recording that failed validation. They can do this straight from the validation error, or later from the failed recording in their Activity Log.
In the request, users can:
- Correct the trip date, arrival time and distance
- Update the origin and destination (where enabled) and the trip type (where configured)
- Add a short explanation of up to 500 characters
Either the driver or a rider can submit. The first person to submit creates one shared request for everyone in that recording, so the other participants don't need to send their own.
Example: Marcus is driving a carpool. Right after Elena gets in, Marcus's phone battery dies and the trip can't be ended properly. In the app, Marcus sees the failed recording and taps Request manual review. Marcus writes "After Elena got in, my phone battery died," selects the correct addresses, enters the distance and taps Request. The request now shows up in your Trips list.
Find review requests
Review requests appear on the Trips page as soon as a user submits them.
- In the Management Dashboard, select Trips in the left sidebar.
- Filter or sort the Status column to show Manual review requested.
- Check the date filter. Requests are listed under the trip's proposed date, not the date the user submitted the request.
Requests also appear in the affected user's own trip list, which is handy when you're already looking at a specific user.
☝️You need permissions for every participant on the trip. If a request includes people outside your access, it won't appear in your list.
Review and correct a request
Open a request to see what happened and fix the trip details before you decide.
- Select the pen icon at the end of the row to open the editor.
- Read the user's explanation and check the original validation results:
- Did the user's own recording succeed?
- Did the driver or partner record successfully?
- Could the system verify that they traveled together?
- Correct the trip details if needed:
- Date and time
- Route (origin and destination). Changing the route recalculates the distance, or you can enter the distance manually.
- Trip type and any available additional travel modes
- Check the participants. You can add or remove people and choose who was the driver. The person who submitted the request must stay included.
- Select Save to keep your corrections. The request stays pending until you confirm or reject it.
Confirm or reject a request
Once you've reviewed the details, one choice in the status dropdown settles the request.
- Open the request with the pen icon.
- In the status dropdown, choose Confirm or Reject.
- If you reject, you can add an optional explanation of up to 500 characters. Users see your explanation, but not your name.
| Action | What happens to trips | What users see |
| Confirm | Missing trips are created and partner links are updated. Details you changed are applied to existing trips, which are reused, not duplicated. | An in-app notification (and a push notification where enabled) that opens their new trip |
| Reject | Existing credited trips stay unchanged. | An in-app notification (and a push notification where enabled) that opens the recording details and your explanation |
| Save only | No credited trips change. | The request still shows as pending in their Activity Log |
Removing participants: If you remove someone who already has a credited trip, that trip may be deleted when you confirm. A removed participant without credit receives a rejected outcome. Participants who were already credited don't get another notification just because their trip was included.
Delete a request
With the right permission, you can delete pending or rejected requests. Delete them one at a time, or select several and use the bulk deletion controls on the Trips list. Rejecting or deleting a request doesn't let the user submit a new one for the same recording.
Edit other past trips
The same editor lets you correct any past trip in the Trips list, not only review requests.
Example: A user logged last Tuesday's commute as a walk, but they actually biked. They ask you to fix it via email so they get rewarded for the bike challenge.
- Select Trips in the left sidebar.
- Search for the user or the trip, and make sure the date filter includes the trip date.
- Select the pen icon at the end of the row.
- Change the trip type or other details, then select Save.