Why does it matter which site the hours went to?
Because one day of hours feeds three different numbers, and each one needs the split:
- Job costing. Labor is usually the largest cost you control. If Tuesday's 8 hours go to the kitchen remodel when 3 of them were on the deck, the kitchen looks worse than it is and the deck looks better, and you will price the next deck wrong. See how to job cost a construction project.
- Client billing. On time-and-materials work, the client pays for hours on their job, at your bill rate. Billing the wrong job is either money left on the table or a dispute.
- Payroll. The worker is paid for all hours worked in the week, on every site, at their pay rate. Payroll does not care which job; it cares that nothing is missing.
The hour on the client's invoice and the hour on payroll are not the same number. Billing can exclude the drive or the shop time; payroll cannot. Keeping the per-site record lets you produce both from the same data.
Is travel time between job sites paid?
Yes. Under 29 CFR 785.38, travel from job site to job site during the workday must be counted as hours worked. The same section counts travel from a place the worker must report to, like the shop to load materials, to the site.
What is not work time is ordinary home-to-work travel: from home to the first site and from the last site home, even if the site changes (785.35).
This is the common mistake with per-site punching: the worker clocks out at site A at 11:40 and clocks in at site B at 12:10, and the 30-minute drive disappears. If you split the day with punches, decide how the drive is paid:
- Pay the gap between the clock-out at one site and the clock-in at the next, or
- Have the worker stay clocked in and only change the job, if your system allows that, or
- Assign the drive to a "travel" or overhead line so it is paid but not charged to either job.
Whichever you pick, write it down and apply it the same way to every crew.
What are the ways to track hours by site?
There are four common methods. They differ in who writes the time down, and when.
| Method | How it works | Where it breaks |
|---|---|---|
| Paper timesheet | Each worker writes start, stop and job per day. | Filled in at the end of the week from memory; job names vary; the office retypes everything. |
| Foreman log | The foreman records the crew's hours and the job. | Works for one crew on one site. When people split off, the foreman is not there to see it. |
| Punch per site | Workers clock in and out at each site, on a clock or an app, choosing the job. | Picking the wrong job from a list; the drive between sites is lost if nobody pays the gap. |
| GPS geofence | Each punch records location and is matched to the site's boundary. | Needs sites set up on a map; a punch from the supply house needs a review rule. |
A geofence does not have to mean tracking people all day. Some apps follow the phone continuously and punch when it crosses a line; others read the location only at the moment of the punch. The second answers "which site, and was the person there" without a record of where your crew drives after work. Read more about how a geofence time clock works.
How do you split one worker's day between jobs?
Use the clock times, then assign each block. Here is a typical day for one carpenter:
- 6:45 to 7:15: shop, loading lumber (required stop, so paid)
- 7:15 to 7:40: drive to the Smith deck
- 7:40 to 11:40: Smith deck
- 11:40 to 12:10: lunch, fully off duty (unpaid)
- 12:10 to 12:35: drive to the Lee kitchen
- 12:35 to 3:45: Lee kitchen
Paid time is 6:45 to 3:45 minus the 30-minute lunch: 8 hours 30 minutes. For job costing, Smith gets 4h 00m and Lee gets 3h 10m directly. The remaining 1h 20m (shop and two drives) is paid labor that belongs to someone: either spread it across the two jobs in proportion, or carry it in overhead. Both are defensible. Mixing methods between jobs is what makes jobs impossible to compare.
To try the numbers for a whole week, use the free timesheet calculator.
What should the record for each site include?
For each block of time, you want enough to answer a question months later:
- Who, and on which date.
- Start and stop time, as recorded, not as remembered.
- The job site, ideally checked against the location rather than picked from memory.
- Who changed it, when, and why, if it was corrected. A corrected time that overwrites the original leaves you with no way to show what happened.
The FLSA does not require you to record the job, only hours per day and per week (29 CFR 516.2), but the job is what makes the hours useful for costing and billing. Remember too that hours on all sites in a week are added together before overtime is figured (778.103). See the FLSA timekeeping requirements for the full list.
How do you get a crew to actually punch at each site?
Make it one step, and make the reason clear.
- Keep it to one tap. If changing sites takes a form, it will be skipped.
- Explain it as pay, not surveillance. The punch at the next site is how the drive gets paid. That is a reason a crew cares about.
- Use the crew's language. Instructions in English only, for a crew that reads Spanish or Portuguese, produce wrong punches.
- Plan for no signal. Basements and new subdivisions often have none. A system that refuses the punch teaches people to punch later, from memory.
- Review weekly, not monthly. A missed punch is easy to fix on Friday and almost impossible after payroll closes.