Time tracking that crews actually use
Every contractor has tried time tracking. Most have given up. The number of paper time sheets that hit the office on Monday morning, partially filled out, in pencil, with one Tuesday written as Thursday, is depressingly consistent.
We've watched customers go from 30% adoption to 96% by changing three things. None of them are 'lecture the crew.'
1. Make clock-in the first thing they see
If the crew opens the app and the first screen is 'Today's jobs,' they'll just look at the job and never clock in. If the first screen is a big 'Clock in' button on the job they're scheduled for, the friction drops to zero.
We changed the mobile dashboard six months ago and adoption jumped 18 percentage points in two weeks. Same app, same workflow, just one click instead of three.
2. Stop asking them to remember which job
The dropdown-with-30-active-jobs is a recipe for misallocated hours. If the schedule says they're on Patel-kitchen today, the clock-in button is for Patel-kitchen. No dropdown.
If they're actually on a different job (rare), they can override — but the default has to be right.
3. Show them their paycheck
The killer feature isn't enforcement, it's transparency. Crew members who can see 'this week you've logged 32 hours at $32/hr = $1,024' clock in religiously. They're double-checking the math before payday.
Crews that can't see their hours assume the office is shorting them. Crews that can see them know exactly what they're earning and trust the process.
What doesn't work
Geofencing. Crews resent it. The 5% gain in accuracy isn't worth the morale hit.
Penalties for not clocking in. You're already paying them — adding stick on top of carrot just makes them quit.
Reminders pushed to their phone. Notification fatigue is real. Three nags a day is two too many.
The actual workflow
Crew member shows up at the job site. Opens app. Sees 'Patel kitchen — Clock in.' Taps. Done. End of day, taps 'Clock out.' Done. Hours land on the right job, marked billable, ready for the next invoice.
If you can't describe your time-tracking workflow in two sentences, your crew can't either.
What 96% looks like
For a 10-person shop with mixed service + project work, 96% adoption means about 8 forgotten clock-ins per month, scattered across the whole crew. Office spends fifteen minutes a week reconciling. Down from a full day on paper time sheets.
That fifteen minutes is what time tracking is supposed to feel like.
The onboarding session matters
Adoption isn't built by mandate — it's built by the first 15 minutes. The shops that hit 96% spend a Monday morning walking each crew member through clock-in on their own phone, watching them do it once, and answering questions. Total time: about an hour for a 5-person crew.
The shops that struggle skip this step. They send a Slack message: 'starting Monday, please clock in.' Adoption sits around 40% forever. The 56-point gap is one Monday morning.
When crews push back
Time tracking is sometimes interpreted as a trust signal. "You don't trust us to log our own hours?" The honest answer: it's not about trust, it's about accuracy. Memory at end-of-week is unreliable for everyone. The crew member who 'thinks' they did 8 hours on Monday and 7.5 on Tuesday is usually off by 30-60 minutes in either direction. That's payroll error and billing error.
Frame it as accuracy, not surveillance. The crew member sees their actual hours, gets paid for actual hours, and the customer is billed for actual hours. Everyone wins. The shops that frame it as 'we don't trust you' get the predictable pushback.
What changes for service vs. project work
Service techs running multiple stops per day need a different flow than project crews running 8-hour shifts on one job. Construction Scope handles both: the service tech opens the app at each stop, picks the customer's job, taps Clock In, finishes the call, taps Clock Out. The project crew clocks in at start of shift and clocks out at end of shift, one job all day.
Both flows need to be available without configuration. If you force service techs to use a project-style flow, they'll just write down their hours on paper and key them in at end of day, defeating the point.
The dashboard the foreman actually uses
End-of-week, the foreman opens Labor & Materials and sees the week's hours grouped by crew member and by job. Approve as-is, edit, or reject. Approved hours flow into the next invoice. Time spent: about 12 minutes for a typical 5-person shop on a Friday afternoon.
The shops that get this wrong are doing approval through Slack messages or screenshots. There's a dashboard, use it. The whole point is having one screen that holds the entire week's labor.
The single biggest lesson
Time tracking is a workflow problem, not a software problem. The software has been good enough for ten years. The workflow has been wrong for thirty. Drop the friction. Show the math. Pay accurately. Adoption follows.