Timesheets, overtime, and pay

Nobody fills in a timesheet from memory on Friday. Hours are derived from the workday the app already watched: route start, stops, breaks, route finish.

How hours are built

Timesheets run weekly, Monday through Sunday. For each route day, on-the-clock time runs from when the tech started their day to when the route completed, minus logged breaks. Techs log breaks with a tap on their route screen; those minutes come straight off paid time.

The tech reviews the week, fixes anything odd, and submits; you approve. Derived-but-reviewable beats both "trust the memory" and "trust the robot blindly".

The setting that moves real money: pay start location

Per company, you choose where the paid day begins:

• Business location: the clock effectively starts from the shop. The classic "paid from the yard" model.
• First stop: the commute-like drive to the first pool is unpaid; pay runs from the first stop onward.

This single setting changes every tech's paycheck math, so set it to match what you actually promised people, and change it only with an announcement.

Overtime

Hours over 40 in a week pay at time-and-a-half automatically. Two nuances:

• PTO hours never count toward the 40. Paid, yes; overtime fuel, no.
• Rates are frozen at submission. The approved week's dollars are a snapshot; a later change to someone's pay rate never silently rewrites an old timesheet. What you approved is what it stays.

Ripple effects

• Break logging is not just pay math; break minutes also keep the day's route-progress and "ahead or behind" indicators honest.
• The timesheet is an employer record. It survives a tech deleting their account, because payroll history is your obligation, not their profile.

Weekly rhythm that works

Techs submit Friday afternoon, you approve Monday morning with coffee, export if your payroll wants a file. Ten minutes a week, and the "what hours did I work" conversation disappears from your life.