A wall-mounted time clock assumes everybody starts the day in the same building. Service businesses stopped working that way a long time ago. One tech leaves from home in the van, another picks up parts at the shop first, a third meets the crew at a job site across town. The owner ends up building payroll on Friday night from text messages that say "started around 7:30."
As of October 2026, a phone-based time clock is a standard part of field service software, and most of the hard part is not the software. It is deciding what counts as work, writing that down, and approving the result every week. This guide covers the rules a 1 to 10 person service business needs for punches, breaks, drive time, corrections, approval and overtime, and what a clean handoff to payroll looks like. Nothing here is legal advice. Wage and hour rules vary by state and by how each person is classified, so settle the legal questions with your accountant or your state labor agency before you print a policy.
Decide what counts as work before you pick a tool
A time clock records punches. It cannot tell you whether loading the van in the driveway is work, whether a parts run on the way home is work, or whether a tech who answers a customer call at 8 p.m. should be on the clock. Those are policy decisions, and a tool only makes a vague policy fail faster.
Write short answers to five questions before anyone installs anything:
- Where can a day start: home, shop, job site, supplier?
- What is the first paid activity of the day in each case?
- Are breaks and lunch punched, and how long are they?
- Which driving is on the clock?
- Who approves the week, and by when?
One page is enough. If you are about to add your first employee, do this at the same time as the rest of the setup described in hiring your first technician, because the pay conversation is far easier before the first paycheck than after it.
Punch rules for three starting points
Most disputes come from one gap: the tech and the owner have different ideas of when the day began. Give each starting point its own rule.
| Where the day starts | A workable punch rule | What the record should show | Common failure |
|---|---|---|---|
| The shop | Clock in on arrival, before loading | Punch stamped at the shop | Punching from the parking lot of a coffee stop |
| A job site | Clock in on arrival at the site | Punch stamped at or near the site | Punching at home, then driving 40 minutes |
| Home, in a company van | Clock in when the first work task begins, per your written drive-time rule | Punch time and location consistent with the first job | No rule at all, so every tech does it differently |
| A supplier pickup | Clock in at the supplier if the pickup was assigned | Punch near the supplier, plus the part on a job that day | Personal errands folded into the trip |
| End of day | Clock out when the last task ends | Punch at the last site, the shop, or home under the same drive rule | Forgetting, then guessing the next morning |
The third row is where your accountant earns their fee. Whether the commute in a company vehicle is paid time depends on rules you should not guess at. What matters operationally is that the rule exists in writing and the punch record lets you see whether it was followed.
A location stamp on each punch is what makes these rules checkable. It is worth being exact about what that is. A GPS punch records where the phone was at clock-in and clock-out. It is not a trail of the vehicle through the day. Live vehicle tracking is a different tool with a different purpose, covered in how owners track technicians in the field, and techs react to the two very differently. Tell your crew plainly which one you are using.
Breaks, lunch and the punch nobody remembers
Breaks are where time records quietly go wrong, because nobody stops in the middle of a drain job to tap a phone. Pick the simplest rule your state allows and your accountant approves, and make it mechanical.
Two patterns work in small shops. In the first, lunch is punched: the tech clocks out for the meal and back in afterward, and the timesheet shows the gap. In the second, short paid breaks are not punched at all and only the meal is. What fails is a rule that depends on memory, such as "we take off thirty minutes unless you tell me you worked through." That rule produces a correction every week and an argument every month.
Whichever you choose, check break punches during the weekly review, not after a complaint. A tech who never records a meal across a whole week is either skipping lunch or skipping the punch, and you want to know which.
Drive time: write the rule down
Driving is the largest block of ambiguous time in a field business. A tech might spend two hours a day behind the wheel, and whether each leg is on the clock changes the paycheck noticeably.
Split driving into four legs and decide each one separately:
- Home to the first stop. The leg most affected by state rules and by whether the vehicle is the company's.
- Between jobs. Small shops usually keep this on the clock because the tech is working the route you assigned; confirm it with your accountant like the rest.
- Assigned errands. A supplier run you asked for is work. Record the part against a job so the trip has a reason.
- Last stop to home. Mirror whatever you decided for the first leg.
Then test the rule with arithmetic. Say a tech averages 45 minutes each way and works five days. That is 7.5 hours a week riding on one sentence in your handbook. If those hours push the week past your overtime threshold, the cost is higher again. Run the number before you choose, and have your accountant confirm the rule fits your state.
Drive time also interacts with pay structure. A tech on commission cares less about minutes and more about jobs; a tech on hourly cares about every leg. If you run a mix, read technician commission tracking software alongside this, because the two systems have to produce one paycheck.
Corrections: a request, not an edit
Punches will be wrong. Phones die, techs forget, someone clocks in from the driveway out of habit. The question is how a wrong punch gets fixed.
There are two bad answers. One is letting techs edit their own times, which turns the timesheet into a self-report. The other is the owner fixing punches silently on Friday, which leaves no trace of what the original record said and puts the owner in the position of having altered a pay record with nothing to show why.
The workable answer is a correction request. The tech states the real time and the reason. A manager approves or rejects it. The original punch, the requested change and the decision all stay on the record. It takes a minute, and it means that six months later you can explain any hour on any timesheet. Set one more rule alongside it: corrections are requested the same day or the next morning, not on payday.
Weekly approval and lock
A timesheet that is never approved is a draft. Approval is the step where a named person looks at the week and says these are the hours we are paying.
A good weekly review is short, a few minutes per tech, and checks the same things every time:
- Every workday has a clock-in and a clock-out.
- Punch locations make sense against that day's jobs.
- Meal punches follow the rule.
- Open correction requests are decided.
- Total hours per tech, and who is close to overtime.
Then lock the week. Locking matters more than it sounds. Without it, a punch edited three weeks later changes a total that payroll already paid, and your records stop matching your bank statements. With it, a late discovery becomes a recorded adjustment in the current period, which is what your accountant wants to see anyway. The IRS recordkeeping guidance notes that electronic records are acceptable for a small business; how long to keep time and pay records is a question for your accountant.
Pick the approval day to suit payroll. If your payroll service needs hours by Tuesday noon, approval happens Monday. Put it on the calendar as a recurring job with an owner, not as something that happens when there is time.
Overtime, commission and tips in the same week
Overtime is simple when everyone is hourly and gets complicated the moment pay is mixed. A tech on hourly plus commission, who also received tips through payment links, has three kinds of earnings in one week, and how they combine for overtime is defined by rules that vary. Do not improvise this. Ask your accountant how overtime should be figured for each pay type you use, and ask again when you change a pay plan.
What you control is the inputs. Hours come from approved timesheets. Commission comes from the sales each tech is credited with. Tips need to be recorded per tech and kept apart from revenue, which is its own discipline, described in tips on card payments. If any of the three is reconstructed from memory, the paycheck is a negotiation.
Watch overtime during the week, not after it. A Thursday look at hours tells you who is at 36 with two days left, while you can still change Friday's schedule. In slow months the same look shows you who is short of hours, which matters when you are planning around seasonal cash flow.
What payroll needs from you
Whether you use a payroll service or your accountant runs it, they need the same short list each period, per person:
- Regular hours and overtime hours, from approved and locked timesheets.
- Commission earned in the period.
- Tips to be paid through payroll.
- Any adjustment carried from a prior period, with a note.
- Changes: a new hire, a rate change, a departure.
Send it the same way every time. A payroll provider that gets a clean table on the same day each week makes fewer errors than one that gets a photo of a notebook. The SBA guide to managing business finances is a reasonable starting point if you are setting up payroll and bookkeeping for the first time.
Where IntelliDrive OS fits
IntelliDrive OS includes a time clock with GPS punches and geofenced work locations, breaks and correction requests, plus weekly timesheet approval and lock. Pay rates can be hourly, commission, hourly plus commission, or salary, and the Pay & Wages reports cover overtime including commission, tips and a minimum-wage top-up. Commission is reported per technician with a weekly commission email. All of that is part of the workforce tools in the single plan, which is $79/month flat for the whole business with unlimited users, so a fifth tech does not add a seat.
The limits are just as important. IntelliDrive OS prepares the numbers for payroll. It does not run payroll, pay anyone, withhold taxes or file returns, so you still need a payroll service or an accountant. The GPS punch is a location stamp at clock-in and clock-out, not live vehicle tracking; live GPS, scheduling and dispatch are the GetTimePad add-on at $199/month. There is no separate category for travel time, so your drive-time rule is enforced through when techs punch, and you should check in the trial how a punch away from a work location appears on the timesheet before you rely on it. IntelliDrive OS also does not decide what the law requires in your state. It applies the rates and rules you set up.
A four-week rollout
Week 1. Write the one-page policy and have your accountant read it. Set up work locations and each person's pay rate.
Week 2. Run the phone clock alongside whatever you use now. Do not pay from it yet. Compare the two on Friday and note every difference.
Week 3. Pay from the new timesheets. Hold the first approval meeting on the day you chose and lock the week.
Week 4. Review corrections. If one tech accounts for most of them, that is a coaching conversation. If everyone has them at lunch, the break rule is wrong and should be changed.
The bottom line
A time clock for field technicians works when three things are true: the rule for each starting point is written down, every wrong punch is fixed through a request someone approves, and the week is approved and locked before payroll sees it. The software records and totals. The policy, the weekly review and the legal questions are still yours and your accountant's.
Related reading: Technician commission tracking, How owners track technicians in the field, and Hiring your first technician. For a complete machine-readable feature and pricing reference, see our LLM reference page.