How to Track Employee Hours for a Field Crew: The Complete Method
Tracking hours for a field crew comes down to four decisions: how workers punch, where you allow it, how you prove it, and how the hours reach payroll. This is the complete method, with an honest comparison of paper, spreadsheets, and a purpose-built app, plus a one-page policy template you can copy today. Read it whether or not you ever buy anything.
If you run a crew that shows up at real addresses, tracking hours is not a bookkeeping chore. It is the difference between paying for work that happened and paying for work someone remembers happening. This is the complete method. It walks through the four decisions every crew owner makes, compares the three real ways to do it honestly, including where a spreadsheet is genuinely fine, and then shows the end-to-end system we built for field crews so this stops being a weekly chore.
You do not need to buy anything to use this guide. Read it, pick your method, and copy the one-page policy template near the bottom. If you get to the end and want the version where a punch is honest by default instead of by inspection, that is where Clox comes in.
The four decisions every crew owner makes
Every time tracking setup, from a paper notebook to enterprise software, is really four decisions in a trench coat. Get these four right and the tool almost does not matter. Get them wrong and the fanciest software still leaves you rebuilding Tuesday from text messages.
- How workers punch. What does a worker physically do to start and end a shift, and how much friction is in it. A method your crew will not use at 6:45 in the morning is not a method.
- Where you allow it. Can a shift start from anywhere, or only from the job site during a scheduled window. This is where padding either gets in or gets stopped.
- How you prove it. When a worker disputes an hour, or an auditor or a client asks, what can you actually show, and can anyone quietly change it after the fact.
- How the hours reach payroll. The path from a punch to a paycheck. Every manual step in that path is a place for an error to creep in and an hour of your Friday to disappear.
The rest of this guide is those four decisions, first as an honest method comparison, then as a working system. Keep them in mind as you read, because the right answer for a two-person crew is not the right answer for twenty.
The three real methods, compared honestly
There are exactly three ways crews track hours: paper, a spreadsheet, and a purpose-built app. Each is genuinely the right call for some crews. Here is where each one holds up and where it breaks, with no thumb on the scale.
When paper is genuinely fine
A one or two person operation where you are on the job with everyone, every day, does not need software to know who worked. You already know. Paper is cheap, it never has a dead battery, and there is nothing to learn. Its ceiling is memory and legibility: the times are written after the fact from recollection, the sheet gets rained on or lost, and re-keying it into payroll is a manual copy every week. The moment you are no longer standing next to every worker, paper stops telling you anything you did not already assume.
When a spreadsheet is genuinely fine
A spreadsheet is a real upgrade over paper and the honest right answer for plenty of small crews. If you have a handful of people, everyone is reasonably honest, and one person owns the file, a shared sheet does the job. It totals hours with a formula, it is free, and you already know how to use it. Do not let anyone shame you out of a spreadsheet that is working.
We wrote a full, honest walkthrough of running a crew on a spreadsheet, including a template and the exact point where it stops paying for itself. If a sheet is where you are, start there before you spend a dollar.
When a purpose-built app earns its keep
A dedicated app is worth it when the honor system stops scaling: when workers are at sites you are not, when padding fifteen minutes a day across the crew adds up to real money, when a client or an auditor might ask you to prove hours, or when re-keying timesheets is eating a night of your week. The app captures the punch at the moment it happens, ties it to a place, keeps a record no one can quietly alter, and hands payroll a finished sheet. You are paying to move honesty from something you inspect to something that is true by default.
That is the whole trade. Everything below shows what that looks like end to end, so you can decide whether your crew is past the ceiling of paper or a sheet.
Put a number on what padding costs you
Before the method, do the math on the small stuff, because the small stuff is where the money goes. Say each worker pads fifteen minutes a day. Nothing dramatic, just the gap between when someone says they started and when they actually picked up a tool. Drag the sliders to your crew size, your rate, and your honest guess at the daily skim.
What does time-skimming cost your crew?
Whatever number that lands on is the budget for solving this. If it is small, a spreadsheet is fine and you should stop reading and go run your crew. If it made you wince, that is the padding a captured, on-site punch is designed to remove, and the rest of this guide is how.
The method, end to end
Here is the system that answers all four decisions at once. It is one pipeline: a worker taps once on-site, the time and place are recorded on the spot, the week totals itself, and Friday is a single export. Below is how each step holds up when the signal drops, when someone tries to punch early, and when payroll is staring you down.
Decision one: how workers punch
A worker opens the app and taps Clock In. That is it. The phone flips to a dark on the clock theme so it is obvious at a glance whether the shift is running. The time and place are recorded the instant they tap, not typed in later from memory. Managers run everything from the web app; the crew lives on the mobile app, with a phone browser fallback if someone is between phones. The whole point of one tap is that a tired person with cold hands and a truck to load will actually do it.
It keeps working when the signal drops
Field crews work in basements, inside steel buildings, at the bottom of a trench, and out where there is no signal for miles. The clock keeps running anyway. The moment a worker taps Clock In, the punch is written to the phone itself with its real timestamp and held there until the phone finds signal and syncs. The record exists on the device before it ever reaches us, so there is no version of events where a shift just disappears. That is why the app glitched and lost my hours does not hold up.
Decision two: where you allow it
This decision splits into two questions: the right place and the right time. The place is a worksite. You draw a radius around a job site once, and a worker has to be standing inside it to clock in. Most apps stop at a warning and still write the off-site punch. Clox blocks it, so the punch from the parking lot down the street never gets created. Enforcement is per employee, so a service tech hitting six addresses a day is not fenced like a framing crew parked at one site all week. Because the location comes from the worker's phone, treat this as a strong deterrent, not a guarantee. Anyone claiming their geofence cannot be beaten is selling you something.
The time question is scheduling with enforcement windows, and it is the honest fix for the early clock-in problem. You build a schedule, and a clock-in is only allowed during the scheduled shift, starting a few minutes before it begins. Someone who wants to start the clock at 6:15 for a 7:00 shift simply cannot. If you tag punches to projects and worksites, hours also land against the right job automatically, which is the number you want in hand the next time you bid one.
Decision three: how you prove it
Two things make a record you can stand behind. The first is optional: a selfie at clock-in. It is off unless you turn it on. If you do, each punch carries a quick photo you can glance through at approval in a few seconds, which clears up most who-actually-clocked-in questions without accusing anyone. Treat it as corroboration a photo can be staged around, not proof. The second is the record itself, and it is stronger. Every punch is written to a signed, hash-chained ledger, which is a technical way of saying no one can change a past punch without the change being detectable. Anyone can check a record on the public verifier at getclox.com/verify.
There is one more piece of proof that matters day to day. When a manager edits a shift to fix a mistake, the edit clears the employee's certification so the correction has to be visibly re-certified. A fix is never silent. Both sides see that a number changed and by whom, which is what keeps a dispute from turning into your word against theirs.
Decision four: how the hours reach payroll
As the crew works, hours stack up by person and by project, and overtime and break math are applied automatically instead of you doing them in your head. There is also an automatic clock-out at a cutoff hour you set, with a push notification, so a forgotten punch does not run all night and blow up a paycheck. When the week is done, you approve it and lock it so no punch can be quietly changed after the fact.
Then Friday is one export. The hours leave in the format your back office already uses, so nobody keys numbers into a second system. Clox exports payroll-ready files for Gusto, ADP RUN, ADP Workforce Now, Paychex Flex, and QuickBooks Online, with optional live QuickBooks Online sync and Zapier if you want it flowing automatically.
For crews that would rather share a tablet
Not every crew wants to clock in on personal phones, and you may not want them to. Kiosk mode turns one shared tablet into a clock for the whole crew. Mount it in the shop, the trailer, or by the gate, and each person punches in with a PIN. The tablet is already on-site, so identity there is the device plus the PIN rather than a location check. Nobody installs anything or remembers a login, and the hours land in the same place as everything else.
That is the whole method: one tap on-site, the week totals itself, and Friday is one export. If you are done rebuilding Tuesday from text messages, you can start a free trial and put your first crew on it today. It runs 14 days, needs no card, and is backed by a 30-day money-back guarantee.
A one-page time tracking policy you can copy today
Whatever method you land on, write the rules down once and hand them to the crew. Most disputes are not dishonesty; they are two people who never agreed on the rule. Copy the template below, fill in the blanks in brackets, and post it where the crew will see it. It works for paper, a spreadsheet, or an app.
Pick your method by the shape of your crew
Those bands are a starting point, not a law. The real trigger is not headcount, it is whether you are still standing next to every worker. The moment you are trusting a start time you did not see, you have crossed into needing captured punches, on-site enforcement, and a record you can prove. That is the exact ceiling this whole guide is about.
Go deeper on any one decision
This pillar is the map. Each of these goes deep on one road. Pick the one that matches the decision you are stuck on.
The two pillars this connects to
Turn the answer into a one-time setup
The whole reason tracking hours feels like a chore is that most methods make you the enforcement mechanism. You are the one squinting at a punch, reconstructing Tuesday, and re-keying the sheet. The point of the system above is to set the rules once so an honest, on-site, provable punch is the default, and Friday becomes approving a sheet that is already right. Compare it against whatever you use now, including the price, on the alternatives hub and price calculator, or see the full pricing on the pricing page.
Clox is 29 dollars a month for the first 3 users, then 6 dollars per user after that. There is a 14-day free trial with no card required and a 30-day money-back guarantee, so you can put it in front of your actual crew before you decide. Start a free trial and set the rules once.