Trusso logoTrusso
All articlesCrew

How to Track Employee Time Across Multiple Job Sites

The Trusso TeamNovember 13, 20266 min read

A guy on your crew works 8 hours today. Maybe 5 of those hours were on the Hartley kitchen remodel, 2 were driving to and from a second site to drop materials, and 1 was spent waiting on an inspector who showed up late. If your timesheet just says "8 hours, Tuesday," you've captured almost nothing useful. You know what you paid him. You have no idea what each job actually cost.

Once a crew is bouncing between two, three, or more job sites in a week, "time on the clock" stops being a payroll question and becomes a job-costing question. The fix isn't more paperwork — it's attaching every hour to a job, not just a day.

{"h2":"Why Time Has to Attach to a Job, Not a Day"}

Most small shops track time well enough to run payroll and badly enough to never know which jobs made money. A daily total tells you labor cost for the week. A per-job total tells you whether the $3,400 kitchen estimate actually covered the labor it took, or whether you quietly ate 6 hours of margin because the crew got stuck on a return trip for materials.

Without job-level time, you can't answer basic questions:

{"ul":["Did this job type (say, fence installs) consistently run over on labor compared to what you bid?","Is one crew member slower on certain tasks, or is the estimate itself wrong?","How much of this week's payroll went to billable work versus drive time and waiting?"]}

If you've ever found yourself wondering whether a job type is underpriced, job-level time data is usually the first place to look — not the estimate. For the estimating side of that gap, see the 7 most common estimating mistakes that eat contractor profit.

{"h2":"Clock-In Methods That Actually Work in the Field"}

Pick a method your crew will actually use, not the one that looks best on paper. In order of what tends to hold up:

{"ul":["Job-specific clock-in from a phone. The crew member opens the app, picks the job from today's schedule, and clocks in. This is the only method that reliably ties hours to a job because the job selection happens at the moment of clocking in, not reconstructed later.","GPS-tagged clock-in/out. Useful for confirming someone was actually at the site, and for catching "forgot to clock out" situations before they turn into a paid 14-hour day. Don't use GPS as a replacement for job selection — location alone doesn't tell you which job a multi-property day was spent on.","Paper or group text. Works for a one-truck operation. Falls apart fast once you have two crews on two sites, because someone always forgets to note which site, and nobody reconciles it until payroll day."]}

Whatever method you use, the job has to be picked before or during the work, not guessed at the end of the week. End-of-week reconstruction is where accuracy dies — people genuinely don't remember whether Tuesday was 6 hours at the Miller job or 5.5.

{"h2":"Drive Time Between Sites"}

This is where most job costing quietly breaks. A crew doing two or three stops in a day racks up real drive time, and if that time gets lumped into whichever job happens to be open on the timesheet, that job's labor cost looks worse than it is — and the other jobs look falsely cheap.

Decide up front how you'll handle it, and apply the rule consistently:

{"ul":["Bill drive time to the job it serves. Driving to pick up materials for the Hartley job is Hartley's time, even if the truck is technically between two other sites. Driving from home to the first site of the day usually isn't billable to any job.","Track drive time as its own category if you want visibility into how much of your payroll is going to windshield time rather than paid work. This matters more than people think — a crew spending 90 minutes a day on the road between sites is losing nearly 10 hours a week that doesn't show up as "overtime" but absolutely shows up in your margin.","Don't average it in. If you split drive time evenly across every open job regardless of actual routing, your per-job numbers stop meaning anything."]}

If you're pricing travel into estimates in the first place, it should match how you actually track it after the fact — see how to estimate travel time and fuel costs for service jobs for the estimating-side version of this problem.

{"h2":"Set Rounding Rules Once, Then Stop Relitigating Them"}

Rounding disputes eat more manager time than the dollars involved justify. Pick one rule and write it down:

{"ul":["Round to the nearest 15 minutes, both directions — not always up for the worker and down for the job.","Apply rounding at clock-in and clock-out, not by adjusting the daily total after the fact.","If a crew member is consistently clocking in a few minutes early "to be safe," decide whether that's paid prep time or not, and apply it the same way for everyone."]}

The specific rule matters less than having one rule everyone knows, so nobody's negotiating minutes on a Friday afternoon.

{"h2":"The Weekly Review That Catches Missing Entries"}

Job-level time only stays accurate if someone looks at it before it hits payroll. A 10-minute weekly review catches most of the damage:

{"ul":["Hours with no job attached. Anyone who clocked in and out but never selected a job that day — common when someone's helping on an unscheduled task.","Jobs with no hours logged that you know had a crew on site. This usually means someone forgot to clock in at all, which means that job's true labor cost is understated, not zero.","Daily totals that don't match the schedule. If the schedule shows a 6-hour job and the timesheet shows 9 hours, that's either a real overrun worth knowing about or a clock-out that never happened.","Drive time that looks off. A day with 3 hours of drive time between two sites 12 minutes apart is a tracking error, not a real pattern."]}

Do this review on the same day every week — right before you run payroll is usually too late to fix anything, since you've already paid out and the crew has moved on to other jobs. Catching it the day before gives you a chance to ask the crew member directly while it's still fresh.

{"h2":"Where This Connects to Your Other Numbers"}

Job-level time is only useful if it feeds somewhere. It should show up against the estimate's labor line so you can see which jobs ran over and by how much, and it should roll into your actual job cost so profit numbers aren't guesses. For the breakdown of what a timesheet needs to capture in the first place, see timesheets for small contractor crews: what information should you capture, and for turning hours into an actual profit number, see how to calculate profit on a contractor job after expenses.

Trusso ties clock-ins to the specific job on a crew member's schedule, so time logged in the field lands against that job automatically instead of getting reconstructed later from memory or a group text. It won't fix a crew that refuses to clock in, but it removes the step where accurate job-level time depends on someone doing extra data entry after the fact.

Run your business the simple way

Try Trusso free for 14 days and send your first estimate in minutes.

Start 14-Day Free Trial