How to Track Hours for Remote and Field Employees Who Work Offsite
Your people are never in one office, so the office clock never fit them. This walks through tracking hours for a scattered, mobile crew: punches that survive dead zones, a phone-browser option with nothing to install, and rules set per person instead of one blanket policy.
JULY 10, 2026 · BY THE CLOX TEAM
Your problem isn't that people are late or padding hours. Your problem is that they're never in the same place twice. A tech starts at a house, drives to a supply house, then a second job, then a call-back across town. A framing crew is on a slab with no walls yet, let alone a wall clock. There's no front door to walk through and no punch card by it. So the honest first question isn't which app is best. It's how you capture hours at all when the work happens everywhere except where you are.
This is a how-to for that exact situation. It's written for the owner who has tried texting timesheets, a group chat, and a spreadsheet at the end of the week, and found that all three leak. We'll cover the three things that actually decide whether tracking a mobile crew works: what happens when the phone loses signal, how someone clocks in without you installing anything on their phone, and how you set rules per person so the guy driving to six sites isn't treated like the crew parked at one.
The short version
Give each person a one-tap clock-in on the phone they already carry. Make it work offline so a dead zone doesn't cost you a punch. Skip any install by letting people clock in from a phone browser. Then set enforcement per person, because a roving tech and a stationary crew aren't the same job.
01
Why the usual methods leak for a scattered crew
None of these are stupid. They're what a reasonable owner reaches for first, and each one breaks in a specific way once people are spread out.
The common ways crews track mobile hours, and where each one falls down.
The thread through all four is the same. When the tool assumes people are in one place with a signal, a mobile crew has to work around it, and every workaround is a place hours go missing or get invented. If you're still on a spreadsheet and it's mostly holding, that's fine and we say so in the spreadsheet guide. This post is for when the crew has outgrown it.
02
The three things that actually make it work
You don't need a big system. You need the three things a mobile crew breaks. Get these right and tracking hours stops being a weekly chore and becomes a setting you turn on once.
1. Punches that survive dead zones
This is the one that quietly ruins most tools. A basement, a steel building, a rural road, a parking garage under the job. The phone drops signal at the exact moment someone taps to clock in. A tool that needs the network right then either loses the punch or writes the wrong time when it finally connects.
The fix is to save the punch on the phone with its real timestamp the instant it happens, and sync it when signal returns. The worker taps once, sees it register, and drives on. Minutes or hours later, when the phone finds coverage, the punch uploads with the time it was actually made, not the time it managed to reach the server. In Clox this is how clock-in works by default. There's no offline mode to remember to switch on.
Why the timestamp matters more than the sync
Some tools go offline but stamp the punch when it reconnects. That's worse than useless on a job site, because the recorded time is whenever the truck happened to hit a bar of signal on the highway. The number to check is whether the real punch time is captured on the device, not on the server. If it is, a dead zone is a non-event.
There's a fuller walk-through of the offline flow, including what the crew sees while they're out of coverage, in the dedicated post below.
2. Nothing to install, if that is the blocker
Half the friction of rolling out any crew app is the rollout itself. Someone has an old phone with no storage, someone declines to install a work app on a personal device, someone is a subcontractor you'll use for two weeks. Making an install mandatory is how a good tool dies in week one, with three people onboard and the rest still texting you.
So Clox doesn't require one. There's an iPhone app on the App Store and an Android app on Google Play for people who want them, and there's a phone-browser option for everyone else. A worker opens app.getclox.com in the browser they already have, signs in, and clocks in from there. No download, no store, no storage argument. For a rotating cast of subs and short-term help, this is often the whole answer. You send a link, they tap it, they're tracking time.
Which one should a person use
If someone is on your crew week in and week out, the app is the smoother daily experience. If they're temporary, resistant to installs, or you just want the lowest-friction start, the phone browser at app.getclox.com gets them clocking in with nothing to install. You can mix both across one crew.
3. Rules set per person, not one blanket policy
This is the piece most tools get wrong, and it's the difference between a system your crew tolerates and one they fight. A mobile crew isn't one kind of worker. You have people who sit at one site all week and people who touch six addresses a day. A rule that fits one wrecks the other.
Clox makes enforcement a per-employee setting. If you lock clock-in to a job site for a stationary crew, you can leave that lock off for the service tech who is genuinely supposed to clock in from wherever the next call is. The roving people aren't fighting a fence at every stop, and the stationary crew still gets the tighter rule. One crew, two sensible policies, no exceptions to remember. We deliberately don't re-explain how the location side works here; the mechanics of worksite locking live in the geofencing pillar. The point for a mobile crew is simply that you're not forced into one rule for everyone.
A location check is a deterrent, not a guarantee
If you do turn on worksite locking for your stationary crews, be clear-eyed about it. The location comes from the worker's phone, so it makes an off-site punch much harder and refuses the obvious ones, but it can't physically prove where someone is standing. Treat it as a deterrent that raises the effort, and tell your crew that plainly. Sold as surveillance, it breeds resentment. Told straight, it protects the honest majority.
03
A setup that takes one afternoon
Here's the order that gets a scattered crew tracking time by the end of a day, without a training session.
- Add your people. Enter the crew once. Each person gets a way in, whether that's the app or the browser link.
- Decide who is stationary and who roves. This is the one judgment call. Stationary crews can be locked to a worksite; roving techs stay free to clock in anywhere.
- Send the browser link to anyone who won't install. app.getclox.com works from any phone, so temps and subs are covered with a text.
- Do a dry run in a dead zone. Have one person clock in with the phone in airplane mode, then turn it back on and watch the punch sync with its real time. Once you have seen that, you trust the rest.
- Let the week run, then check the numbers. Overtime and breaks are calculated for you, so at week's end you're reviewing hours, not rebuilding them.
That's the whole shift. The work moves from you collecting and retyping times every Friday to the crew capturing their own time as they go, from wherever they are, in a way you can actually check. It's a one-time setup instead of a weekly chore.
04
When payroll comes due
The reason to capture clean hours all week is so the end of it is quiet. Because the punches carry real timestamps and the overtime and break math is already done, the numbers are ready to leave. Clox exports to Gusto, ADP RUN, ADP Workforce Now, Paychex Flex, QuickBooks Online (CSV), and QuickBooks Desktop (IIF), with optional live QuickBooks Online sync and Zapier. You're not transcribing a spreadsheet into a payroll system. You're exporting a file where the totals are already correct.
05
Common questions from crew owners
My people use their own phones. Is that a problem?
No, and that's the normal case. That's exactly why the phone browser exists. Anyone who doesn't want a work app on a personal phone can clock in from app.getclox.com instead, with nothing installed. The people who prefer the app can use the app. It's their choice, not a blocker for you.
What if someone forgets to clock out at a job?
Clox has an automatic clock-out at a cutoff hour you set, with a push notification, so a forgotten punch doesn't run all night and blow up someone's hours. You still see it and can correct it, but the runaway shift is caught for you.
Can I trust times from people I never see?
More than a texted number, yes. Each punch carries the real time it was made, and the record is tamper-evident after capture, meaning a time can't be quietly changed later without it showing. If proving hours to a client or defending them in a dispute is the real worry, that's its own topic, covered below.
06
Where this sits in the bigger picture
Tracking a mobile crew is one piece of tracking employee hours in general. If you want the full method, from choosing an approach to running it week to week, start with the pillar. If your crew is specifically multi-site or in the trades, those spokes go narrower.
- How to track employee hours, the full method this post is one part of.
- How to track hours across multiple job sites, when the same crew moves between sites and hours must land on the right job.
- The best way to track time for a small crew, keeping it simple when the crew is small.
If a phone your crew already carries, punches that survive dead zones, a browser option with nothing to install, and rules set per person sound like the fit, you can start a free trial and have your first scattered crew tracking time this afternoon. It's 14 days free, no card to start, with a 30-day money-back guarantee. Add one person, send the browser link, and try a punch in a dead zone before you commit anyone else.