A crew accepts time tracking when you get three things right, and quietly abandons it when you miss any one of them. Explain the real reason before you install anything (hours that never make it onto an invoice, and quotes built on guessed time), and be explicit about exactly what it records, location included, before anyone finds it for themselves. Make clocking in take one tap in a driveway with a ladder on your shoulder, because anything harder gets skipped. Then read the timesheets without nitpicking minutes: the day you question someone's twelve minutes is the day the app becomes the leash they suspected it was.
You announce it at the end of a Friday: "Starting Monday we're putting an app on the phones to track time." Your best lead installer (nine years in, the one who opens jobs without being asked and closes them without being chased) goes quiet. Then, half a joke, not really a joke: "So you're going to watch us now?"
That sentence is the whole problem, and it deserves a better answer than "it's just for payroll." Because he is not objecting to writing down his hours. He has written down his hours his entire career, on cards, on whiteboards, on the backs of supplier receipts. He is objecting to being monitored, and he is right to be suspicious, because plenty of tracking tools are built exactly for that: breadcrumb trails, idle alerts, a dashboard where the boss watches dots move around a map.
You can get a crew to accept time tracking, including the proud ones, including the nine-year guys. But you have to earn it three ways: with the pitch, with the friction, and with how you behave when you read the timesheet. Miss any one of the three and the app dies in a month, not through refusal, but through forgetting, which is refusal's polite cousin.
Why does your crew push back on time tracking?
Start by taking the objection seriously, because it is not paranoia.
A tradesperson's day is full of things that look like slack and are not: the twenty minutes at the supplier counter, the drive between jobs, the conversation with the homeowner that keeps a $9,000 project from turning into a complaint, the hunt through the van for the right fitting. A surveillance tool flattens all of that into "not working." Anyone who has done the job knows this, which is why the people most offended by monitoring are usually your best people. They know how much invisible work they do, and they know a dashboard will not see it.
There is also a simpler thing underneath: being tracked feels like being distrusted, and your lead installer has nine years of evidence that he does not need watching. Installing a watcher anyway reads as a demotion. If the tool you pick actually is a watcher (location trails, screenshots of movement, minute-grading), then his reading is correct and no pitch will fix it.
So the first decision has nothing to do with which app. It is about what kind of thing you are installing: a clock, or a leash. Pick the clock.
The drive cost calculator shows what the drive to a job costs you, per job and across a year.
What is time tracking actually for?
Here is the honest case, and it has nothing to do with catching anyone.
Billing accuracy. If you bill any time-and-materials work, every unrecorded half hour is money you did the work for and did not charge. A crew of three leaking twenty minutes a day each (not stolen, just unremembered by invoice time) is roughly an hour a day of finished work that never lands on an invoice. At a blended $85 an hour, that is over $400 a week, more than $20,000 a year, gone without anyone doing anything wrong. Memory is the thief, not the crew.
Quoting accuracy. Fixed-price work needs the clock even more, just for a different reason. If you do not know that bathroom demos actually take your crew eleven hours and not the eight you keep quoting, you will keep pricing them wrong forever, and you will misdiagnose the loss as slow work when it is actually a wrong number. Real hours against real jobs is the only feedback loop that fixes your estimates. The clock is not grading the crew; it is grading the quote.
Getting paid correctly. This is the crew's side of the same coin, and it is the part worth saying out loud: an accurate clock protects their paycheck. No more reconstructing Tuesday on Friday afternoon, no more losing the half day that got split across three jobs, no more "I thought you left early that day" conversations. The sheet remembers so nobody has to argue.
Notice what is absent from the list: a trail of where the truck drove all day, how fast anyone walked, whether they stopped at a coffee shop. None of that improves an invoice or a quote. A tool that collects it is collecting it for some other reason, and your crew will know.
Say it before you install it
The rollout conversation matters more than the app choice, and it takes two minutes. The mistake is announcing a policy; what works is explaining a problem. Something like:
"Here's the deal. We're losing billable hours because we reconstruct time from memory at invoicing, and I'm quoting jobs off hours I'm basically guessing. So we're going to clock in and out per job: one tap when you start, one when you stop. It's a clock, not a tracker: it doesn't follow the truck around all day. It does stamp where you were at the punch itself, and I'm telling you that now rather than letting you find it, and I'm not grading anyone's minutes. It's so the invoice matches the work and the next quote matches reality. Your hours are your hours. If the sheet says it, that's what you're paid on."
Every clause in that speech is a commitment you will be held to, so only say the parts you mean. The three that matter most: there is no all-day tracking, nobody gets nitpicked over minutes, and the sheet is believed. Break any of them once and the crew's original suspicion is confirmed permanently. You do not get a second launch.
One more move that costs nothing: go first. Clock your own time on jobs for a week before asking anyone else to. It converts "a thing the boss imposed" into "a thing we do here," and it gives you a preview of every friction point before your least patient installer finds them for you.
Friction decides whether it survives
Whatever tool you choose, the physics are unforgiving: clock-in has to be nearly free, because it happens at the worst possible moment. Nobody starts a job at a desk. They start it in a driveway with a tool bag on one shoulder and a ladder coming off the rack. If starting the clock takes finding the right screen, waiting for a login, choosing from forty jobs, and confirming twice, it will be skipped. Not defiantly, just naturally, the way anyone skips a pointless-feeling chore while holding a ladder.
And skipped punches are worse than no system at all, because now the sheet is sometimes wrong, which means you are back to reconstructing from memory, except now there is a half-right record to argue with.
The bar to hold any tool to: one or two taps from pocket to punched in, on the job you are actually standing at. It has to work with no signal (basements, rural sites, concrete buildings) and sync later, because "the app needed bars" is the first excuse that becomes the permanent excuse. Forgotten punches need a graceful fix: someone will genuinely forget, and if repairing a missed clock-out is a chore or an interrogation, people quietly stop punching at all. The repair should be as boring as the punch.
How to read a timesheet without becoming the boss they feared
The tool is installed, the pitch was honest, punches are landing. Now comes the part where most owners quietly break their own promise: the first time they look at the data.
Do not nitpick minutes. The sheet will show a 7:12 start where you expected 7:00, a 26-minute gap between jobs that maps to a 20-minute drive. If you bring that to a crew member, you have just announced that the clock was a leash after all, and you have spent your entire credibility on twelve minutes. Individual punches are noise. Treat them as noise.
Do look for patterns. Patterns are where the real information lives, and almost none of it is about effort. Every install runs three hours over the quote: your quote is wrong. Mornings hemorrhage forty-five minutes before the first punch: your dispatch or your supplier routine is broken. A scheduling problem, not a character problem. One crew member's sheets are chronically incomplete: that is a habit conversation, made once, about punching, not about the hours themselves.
Pay what the sheet says. This is the covenant that makes everything else work. If the sheet says 43 hours, pay 43 hours. Do not shave the Friday punch you privately doubt. The moment you edit downward, the sheet stops being a record and becomes an opening bid, and your crew will start padding it defensively, and they will be right to. If you genuinely believe an entry is wrong, have the conversation and fix it with the person, forward-looking, in the open.
Share the wins back. When the clock data fixes a quote or proves a job made money, say so: "the sheets showed demo runs eleven hours, so I priced this one right and we're not eating three hours Friday." The crew handed you that number. Showing them what it bought is how the clock stops being your tool and becomes the shop's.
The first two weeks
Expect imperfection and say so in advance. For the first two weeks, punches will be missed daily; fix them without ceremony and keep the tone boring. Resist the urge to look at the data at all for the first week. There is nothing in five days of noisy punches worth a conversation, and every early comment you make gets amplified by a suspicious audience. By week three, the punch is muscle memory for most people, and you will have exactly one holdout. Handle the holdout privately and as a habit issue, the same way you would handle someone who never fills out the fuel log. It is not a referendum on the system.
Where Zeus draws the line
Zeus's time tracking is built on the clock side of the line described above. Team members clock in and out per job (a tap against the job they are on) and the hours land on per-job timesheets, so billing and job costing get real numbers instead of Friday reconstructions. It works offline and syncs when there is signal, which matters for exactly the basements and rural sites where punching otherwise gets skipped.
And the boundary is deliberate, but it needs to be stated precisely rather than reassuringly. Zeus records a location stamp at the moment of clock-in and at clock-out, and the timesheet shows how far each punch was from the job site. What it does not do is run in the background: no drive or mileage log, no breadcrumb trail between punches, no live map of where your crew is right now. Say that version to your crew, in those words, before they find the timesheet themselves. Payroll itself runs wherever you run payroll; Zeus's job is to make sure the hours feeding it are true.
If you make the honest pitch from this article, it helps to be able to hand your lead installer the phone and walk him through exactly what the sheet holds and what it does not.
Frequently asked questions
My crew is paid salary or day rate. Do we still need per-job time?
Yes, but be clear about why, because the pitch changes. With no hourly pay at stake, the clock is purely a costing tool: it tells you what jobs actually consume so your quotes stop lying to you. Say exactly that. Crews accept "this fixes our pricing" far more easily than a vague "we need visibility."
What about drive time between jobs?
Decide the policy before the tool arrives, tell everyone, and apply it evenly. Whether drive time is on the clock (and to which job) varies by shop and by local employment rules, which differ by province and state. The system does not care which policy you pick. It cares that the policy is explicit, because ambiguity is where both resentment and padding grow.
Someone is obviously padding their hours. Doesn't "pay the sheet" mean I just eat it?
No. "Pay the sheet" means you do not silently edit; it does not mean you do not talk. Padding shows up as a pattern (consistently long punches against jobs that finish light) and patterns are exactly what you are allowed to raise. Bring the pattern, ask for the story, and fix it forward. What you never do is quietly dock hours, because that converts one person's padding into everyone's distrust.
Should I ask the crew to also log what they did, not just the time?
Keep the punch itself frictionless. Adding required notes to every clock-out is how you lose the punch entirely. If you need a record of what happened on site, keep it separate from the clock: a short end-of-day note per job covers inspections, discoveries, and disputes without taxing every start and stop. One tap to punch; words only when words are needed.
ZEUS