A usage-based rideshare split charges each person only for the trips they actually took, instead of dividing that week's full fare by headcount. Equal split is quicker to run.
That's a real gap on group trips. Someone only rides from the airport, then stays in, while someone else stacks late drop-offs all week.
Can a spreadsheet split each fare by who actually rode?
Yes. You log every ride, give each rider a row, divide that fare by the people in that car, and let SUMIFS add the shares by name. The payer then collects those totals.
Thing is, the formulas only stay honest if names match and the group already agreed that being in the car is the rule.
Equal split is faster, not always fair
Equal split takes the trip total and divides by how many people are on the vacation. That works when everyone rode together every time.
Usage-based split prices each ride separately. A $30 car with three people is $10 each. The next $20 ride with only two of them is $10 each for those two, and nothing for the friend who stayed in that night. Add the shares at the end. That sum is what each person owes the person who paid.
Give every rider a row
Don't bury three names in a notes cell. SUMIFS can't read a sentence.
Use one row per person per ride. Three people in one car means three rows with the same date, the same trip note, the same fare, and the same rider count. The rider name is the only difference.
Make a Members tab first. One column of names. The log and the summary both use that list.
| Column | What you enter |
|---|---|
| Date | Day of the ride |
| Trip note | A short label, such as Airport to hotel |
| Total fare | App total, tip included |
| Rider count | People in that specific car |
| Individual share | A formula, not a typed number |
| Rider name | One name from the Members list |
Keep a summary nearby. Names from Members, a Total owed column, and a Paid checkbox.
You'll want the rider count to match the number of name rows you just added for that trip, and if you type 3 in the count but only add two names, the shares on those two rows will be too low and the missing person simply never shows up in the total, which is the kind of quiet error that only shows up when someone opens the receipt and says wait, I thought four of us were in that one.
Log the tip in the fare cell. Log the tip there, not in a comment. Comments don't get summed.
Two formulas, then stop
If total fare is in column C and rider count is in D, put this in the share column:
=IF(D2=0,"",ROUND(C2/D2,2))
Blank counts should not divide. The IF leaves those rows empty. ROUND keeps each share at cents. Copy it down as you add rides.
You can skip dragging the formula down. Put this in E2 and leave the rest of column E empty:
=ARRAYFORMULA(IF(D2:D>0,ROUND(C2:C/D2:D,2),))
On the summary tab, if shares live in E and rider names in F, and A2 holds the person you're totaling:
=SUMIFS(E:E,F:F,A2)
The argument order is in Google's SUMIFS documentation if a range looks off. The function adds every share for that name and skips rides they never joined.
Point SUMIFS at the name cell, not a quoted string. A new person is one Members row plus a copied formula.
This log assumes one person paid in the app. If you rotated payers, add a tiny second table with one row per ride: date, fare, paid by. SUMIFS that table for what each person already covered. Net is their ride shares minus that amount. Don't sum fares on the rider log. That fare repeats on every rider row, so you'd count it three times.
The leftover penny
A $20 fare split three ways shows $6.67 per person, and 6.67 times 3 is $20.01. Let the cardholder absorb the extra cent.
Lock the parts people shouldn't type in
Typos wreck this faster than bad math. Alex and Alex M are two people to SUMIFS.
Select the Rider name column. Open Data validation from the Data menu and point the dropdown at the Members tab. People pick a name. They don't invent spellings.
Protect Individual share and Total owed so a stray delete doesn't kill a formula. Google documents how to protect sheets and ranges if you want only the owner editing those cells while everyone else still logs rides.
When someone swears they weren't in Thursday's car, use version history instead of reconstructing the night from memory. You can see who added the row.
Turns out a lot of those fights are a wrong name on a dropdown.
Agree on the ugly cases before you share the link
The sheet can't invent your group rules. Settle these before the first airport pickup:
- Total fare includes the tip and any booking fee. If it hit the card, it hits the sheet.
- Cancellation fees stay with the person who requested the car, unless the whole group changed plans.
- Log rides by the last night of the trip, not sometime next month.
- Keep cents in the sheet. Round only on the payment request if you want whole dollars.
Close the books
Freeze the file before anyone "fixes" a row.
- Ask everyone to scan Rider name for trips they took or didn't take.
- Set sharing to View only.
- Send requests from the Total owed column, one person at a time.
- Tick Paid as the money lands.
Keep the ask plain: "Your share of the weekend rides is $38.40. I put them on my card. Send it when you can."
to be honest, nobody needs a speech about fairness at that point. They need a number and a sheet they already checked.
If someone brought a plus-one, add the guest as a name or fold them into the friend who invited them. Pick one rule. Use it on every guest ride.
Make the Members tab tonight and paste both formulas. Add one test airport ride with two riders and confirm the summary matches the split you expect. Then share the file, protect the formula columns, and use it on the next real trip.