The Gas field is a calculated value. So is Total Calc. So is Tip Calc. So is Percentage. These aren't fields you type into — they derive from the raw inputs you log per order and per shift. The template is doing the arithmetic so you don't have to, and the arithmetic it's doing is your actual take-home after expenses.
Most delivery couriers have a rough intuition about what a good shift looks like. This template replaces intuition with a ledger.
Driving Without Numbers
A courier running restaurant orders for four hours on a Friday evening generates somewhere between fifteen and twenty-five delivery transactions, each with a subtotal, a possible tip, a card or cash distinction, and a gas cost that's amortized across the shift's odometer reading. Summing those mentally is a rough estimate at best — you know the tips were decent, you think you spent about twelve dollars on gas, and the shift felt like a good one.
That's not data. That's a feeling.
Without a per-shift record, the questions that determine whether this work is actually profitable remain permanently unanswered. Is the Friday dinner rush more efficient than the Saturday lunch shift? Does the route through a specific neighborhood yield higher average tips or lower? Are there customers worth flagging — addresses where the order is reliably a dead run, with no tip, complicated access, or repeated complaints?
None of these questions have answers if the data to answer them was never captured.
Sixty Shifts of Logged Delivery Data
The Date and Shift radio fields let you filter by time period and by shift type simultaneously. After two months, a sorted view by Date tells you which weeks were outliers. Filtering by Shift with high-performing Total figures tells you which shift type consistently produces better net earnings.
The Address entries field is the customer CRM function of this template. A customer's address logged with associated order history, tip behavior (visible in the Tip currency field records), and a Credit multichoice field that can flag payment method or account status transforms the delivery run from an anonymous transaction into a managed relationship. The Street field and location identifiers allow you to cluster addresses geographically — which deliveries are clustered within three blocks of each other versus which ones require a fifteen-minute detour.
The Blacklisted flag — implied by the Credit and customer tracking structure — is the field that prevents you from repeatedly dispatching to an address that historically produces no-tip, long-wait, or disputed-payment outcomes. In a system without this flag, every driver starts every shift with no institutional memory. With it, problem addresses are visible before you accept the order.
Travel time logged as a duration field per delivery is the operational efficiency metric. A $4 tip on a six-minute run is a very different value proposition than a $4 tip on a twenty-two-minute run with parking issues on a one-way street. Without the travel time field, you can't separate those two outcomes — they look identical in the tip column.
What the End-of-Shift Calculation Actually Says
After the last delivery, you're looking at Total Calc — the sum of all order totals minus gas cost across the shift's odometer-derived expense. Percentage gives you the earnings-to-gross ratio, which tells you how much of the money moving through your hands is actually staying in your pocket after the platform fees and fuel expense are accounted for.
Shift: AM. Hours: 6. Orders: 18. Subtotals averaged out. Tips were solid on fourteen of them, zero on four. Gas: $9. Total Calc puts you at $74 net.
That number, logged against the date and shift type, goes into a dataset that eventually tells you whether this job is worth the wear on your car.
The Items list field per order captures what was delivered — useful for any dispute resolution about order accuracy, and useful for identifying which restaurants generate the most complex, time-consuming order-filling interactions at pickup.