Time Tracking for Home Service Crews: Jobs, Drive Time and Timesheets

Ask most owners how long a typical water heater swap or a two-bedroom deep clean takes, and you will get a confident number. Ask what the crew actually spent on the last ten of them, and the answer is usually a guess. That gap is where profit leaks out: jobs quoted at four hours that take six, drive time nobody counts, and paychecks built from memory on a Friday afternoon.

This guide covers why to track crew time per job, how to clock in and out without slowing anyone down, how to handle drive time, and a simple weekly routine for timesheets, approvals and payroll. It includes general information about federal wage-and-hour rules, which is not legal advice.

Why track time per job

• Job costing. Labor is a big part of what every service job costs. Hours per job, times what you pay, tells you what each job really cost and which kinds of work earn the most.
• Payroll accuracy. Paychecks built from timesheets your crew filled in during the week are more accurate than numbers remembered on payday, and easier to explain when someone asks.
• Better quotes next time. After a few months you will know how long a panel upgrade, a gutter guard install or a move-out clean really takes, by crew and by house size.
• Spotting problems early. Repeat visits to the same address, jobs that always run long and techs who are stretched thin all show up in the hours.

A job costing example

Here is a made-up example to show how the numbers work. Say you quote bathroom fan replacements at a flat price that assumes two hours of labor. Your timesheets for the last ten show an average of three hours, mostly because attic access in older homes takes longer.

Now you have choices backed by facts: raise the price for older homes, add an attic access line to the quote, or send a tech who is faster at that kind of job. Without the hours, you would just feel that fan jobs are "not worth it" and never know why.

Clocking in and out per job

The simplest system that works: each tech starts a timer for the job when they arrive and stops it when they leave. A few rules keep the data clean:

• One entry per job visit, started on arrival, stopped on departure.
• A short note on anything unusual: "waited 30 min for homeowner", "second trip for a part", "found extra rot under the flashing".
• Supply house runs go on the job they were for, so the job cost includes them.
• Callbacks and warranty visits get their own entry, marked as a callback, so you can see what rework costs you.
• Shop time (loading the truck, cleaning equipment, meetings) goes on its own entry, not on a customer job.

Missed entries will happen. When someone forgets to start a timer, the fix is a corrected entry with a note, not a guess at the end of the week.

Handling drive time

Drive time is easy to get wrong, both in tracking and in pay. Here is the general federal picture, based on the US Department of Labor's guidance under the Fair Labor Standards Act (FLSA). It is not legal advice, and your state may have different or stricter rules.

• Job site to job site is generally work time. The Department of Labor's fact sheet on hours worked says travel from job site to job site during the workday is work time and must be counted as hours worked.
• The ordinary commute generally is not. The same fact sheet describes ordinary home-to-work travel as not work time.
• Reporting to the shop first changes things. Under the federal regulation on travel during the workday, if a worker must report to a meeting place to get instructions or pick up tools or a truck, the travel from there to the job is generally part of the day's work.
• Overnight and out-of-town jobs have their own rules. Check the Department of Labor's guidance or ask a professional before you send a crew away overnight.

In practice, the easiest approach is to track drive time as its own entry, separate from time on site. Your crew is paid for the hours that count, and your job costing still shows how much time goes to driving. If drive time is eating your day, that is a scheduling problem worth solving: group jobs by area so the crew is not crossing town three times.

Breaks, overtime and records

A few more federal basics from the Department of Labor that affect how you track time. Again, this is general information and state rules can add to it.

• Short breaks count. The Department of Labor says rest periods of short duration, usually 20 minutes or less, must be counted as hours worked.
• Real meal breaks generally do not. Bona fide meal periods (typically 30 minutes or more) generally need not be paid, but only if the worker is completely relieved from duty. Eating in the truck while answering dispatch calls is not a meal break.
• Overtime is weekly. Non-exempt employees covered by the FLSA must receive at least one and one-half times their regular rate for hours over 40 in a workweek. Some states add their own overtime rules.
• Keep the records. The Department of Labor's recordkeeping guidance says employers must record hours worked each workday and each workweek for non-exempt workers. Its fact sheet says records like time cards should be kept for at least two years, and payroll records for at least three.

Whether a worker is an employee or an independent contractor, and whether they are exempt from overtime, are legal questions that depend on the facts. If you are unsure, talk to an employment lawyer or contact the Department of Labor's Wage and Hour Division.

Weekly timesheets and approvals

Time tracking only pays off if someone looks at it. A weekly routine keeps it from piling up:

1. Daily: techs start and stop timers per job and add notes. Two minutes at the end of the day to fix anything missed.
2. End of week: each tech reviews their timesheet, by job and by day, and submits it.
3. Review: you or your office manager check for gaps, overlaps and unusually long jobs. Ask about anything odd while it is still fresh.
4. Approve: once a timesheet is right, approve it. Approved hours are what payroll uses.
5. Look back: once a month, compare hours with what you quoted for your common jobs, and adjust prices or estimates.

Make the approval about accuracy, not suspicion. When techs see that timesheets lead to fair pay and better-priced jobs, they keep them up to date.

Connecting time to payroll

The point of approved timesheets is a paycheck nobody has to argue about. Whatever payroll system you use, the flow should be the same: approved hours for the pay period, split into regular and overtime hours, plus any time off, become the pay run. The fewer times numbers are retyped between systems, the fewer mistakes end up on a paycheck.

Getting your crew on board

• Explain the why. Accurate hours mean accurate pay, including drive time that may have been missed before.
• Keep it to a tap or two. If clocking in takes longer than unlocking the truck, people will skip it.
• Start with one crew for two weeks, fix what is awkward, then roll it out to everyone.
• Use the data to help, not to punish. If a job always runs long, fix the quote or the process before blaming the tech.

A getting-started checklist

1. Decide your entry types: job, drive, shop, callback.
2. Add your current jobs and invite your crew.
3. Write a one-page rule sheet: when to start and stop, how to note a missed entry, how drive time works.
4. Set a weekly submit-and-approve day before payroll.
5. After a month, compare hours with quotes on your top five job types.

Good time tracking makes quoting easier too. Quotes and e-signatures are coming to Yantra Pros, so the hours you learn from your timesheets can go straight into the next estimate. In the meantime, keep your crew busy with maintenance reminders in the slow seasons, and get started with Yantra Pros when you are ready.