A day spent entirely on one job is the easy case — everything that happens that day obviously belongs to that job. The harder, and increasingly common, case is a morning on one site, an afternoon on another, and a quick call-back to a third squeezed in between — where the discipline of tagging everything correctly is the first thing to slip when the day's moving fast.

What actually goes wrong on a multi-site day

  • Fuel and mileage get lumped into one job — usually whichever job was open on the app last, rather than split by the actual driving done for each site.
  • A supplier run for job two gets tagged to job one — because the receipt was scanned in the van between sites, and the app still had the morning's job selected.
  • Time on a quick call-back goes untracked entirely — a 20-minute fix that's too short to feel worth logging, but adds up across a week of similar call-backs.
  • Nothing gets tagged until the evening — by which point which receipt belonged to which site is a guess, not a fact.

The habit that actually prevents this

The fix isn't more discipline in the evening — it's tagging at the point of spend, on the site it happened, before moving to the next one. A receipt scanned in the van outside the merchant, tagged to the job that trip was for, takes the same few seconds whether it's the only job of the day or the third. The problem only shows up when tagging gets deferred to "later," because later is exactly when the details blur.

Splitting fuel and mileage across a multi-site day

Driving between three sites in a day is a real cost that belongs to all three, not just the last one you happened to be thinking about when you logged it. Splitting mileage by the actual leg driven — site A to site B, site B to site C — gives each job an honest share of the day's travel cost, rather than one job absorbing all of it and the others looking artificially cheap to get to.

A worked example

Say a Tuesday runs: a morning finishing a bathroom, a lunchtime materials run for Thursday's kitchen job, and an afternoon call-back to last month's fencing job for a snag. Tag the materials run to whichever job's open by habit and Thursday's kitchen job either gets charged for materials it doesn't need yet, or the bathroom job absorbs a cost that was never really its own. Three separate five-second taps, done at the moment each thing happens, is the entire fix.

How Site Wallet handles this

Switching the active job takes one tap, so a receipt scanned between sites, or a mileage leg logged after a specific drive, gets tagged to the right job in the moment — not reconstructed from memory once the day's three sites have blurred into one long shift.

FAQ

Is it worth tracking a 20-minute call-back separately?

Individually maybe not — but a pattern of frequent short call-backs to the same client or job type is exactly the kind of thing that's invisible unless it's logged, and useful to know when quoting similar work in future.

How should I split fuel when two sites are on the same route?

A reasonable split by distance or time spent travelling to each is good enough — precision to the last mile matters less than not dumping the whole trip on one job.

What if I genuinely don't have a signal to log anything on-site?

Scanning a receipt or noting a mileage leg doesn't need a live connection — most apps queue it locally and sync once you're back in range, so the habit still works even on sites with no signal.