Time Tracking for Concrete and Masonry Crews When There Is No Signal
On a pour day the crew is eight feet down with no bars, and that's exactly when the punch has to land. Here's the offline-first method that keeps every hour.
JULY 11, 2026 · BY THE CLOX TEAM
The concrete truck is scheduled for 7 a.m. and it doesn't wait. Your crew is on site at 6:45, forms are checked, the pump is staged, and for the next few hours nobody is looking at a phone. They're placing, screeding, floating, and finishing before the mud goes off.
That window is the whole job, and it usually happens in the exact places a phone has no bars. Think eight feet down in a foundation, inside a poured basement with rebar overhead, or on a rural build where the nearest tower is a county away.
So the honest problem for concrete and masonry crews isn't that time tracking is hard to understand. It's that the moment you most need a clean punch is the moment the phone can't reach a server.
This guide is about the method that survives that: capture the punch on the phone the instant the worker taps, before any signal is involved, and let it sync later. Get that one thing right and the rest of the week, the labor per pour and the payroll, falls out of it.
01
Why pour days break normal time tracking
Most time trackers only record a clock-in when the phone can talk to the server. On a pour that means one of two things happens, and both quietly rewrite your timesheet.
Either the worker can't clock in at all until they climb out of the hole and back into coverage, or the app waits and stamps the punch at the moment it finally syncs. That might be an hour after the pour actually started, punched in from the cab of the truck on the way to the next site.
The part worth understanding is that GPS and cell signal aren't the same thing. A phone can get its location from satellites with no cell coverage at all. The piece that needs signal is only the upload.
So a tool built for a basement crew should be able to read where and when a worker clocked in with zero bars, and then hold that punch until there's signal to send it. If it can't, the pour day is exactly where your hours go missing.
The distinction that matters underground
Capturing the punch doesn't need signal. Uploading it does. A tracker built for field crews saves the clock-in on the device the instant the worker taps, stamped with its real time, then sends it when coverage returns.
02
The method: capture at the tap, sync when you surface
Here's the workflow that holds up on a pour. When a worker taps clock-in, the phone writes that punch to the device immediately, stamped with the real time of the tap, and drops it in a local queue. It doesn't wait for a connection. The on-the-clock timer keeps running on the phone through the whole pour.
When the crew climbs back into signal, driving out of the site or reaching pavement, the queued punch uploads to your dashboard with its original time and location intact. Stored now, sent later. A dead zone stops being a hole in the timesheet.
Setting this up on your own crew takes an afternoon, not a rollout. You can start a free trial and put your next job on it today. It runs 14 days, needs no card, and is backed by a 30-day money-back guarantee.
What matters on site is that the worker sees a confirmation, not a spinning error. The screen says the punch is saved and will sync, so nobody stands in a trench trying to get a bar of signal before they can start pouring. This is the specific mechanism the rest of this guide leans on, and it's covered in depth, limits and all, in the offline post below.
03
Bill by the pour, not by the week
A concrete crew doesn't think in forty-hour weeks. It thinks in jobs: a footing and stem wall on Monday, a slab-on-grade Wednesday, a block-and-brick lift Thursday, flatwork and a driveway to close the week. The number that decides whether you made money is labor against each of those, not the payroll total. When time is just a lump of hours, you can't see that the retaining wall ate a day and a half of finishing you never bid for.
So the second half of the method is tagging every punch to a project as it happens. The same clock-in that survived the dead zone also carries the job it belongs to, so at the end of the week the hours are already sorted by pour. You see the real labor on each foundation, each flatwork run, each block job, and the next bid starts from what the last one actually took instead of a guess.
The same pile of hours, two ways. Only one tells you which job to bid differently next time.
That per-job breakdown is also what backs up a billing dispute or a change order. When a GC asks what the extra finishing on the wall cost, the labor is already sitting against that job, traced to real punches, not reconstructed from memory. If job costing on a small crew is the angle you care about most, there's a focused piece on it below.
04
Tight windows, weekend pours, and the overtime math
Concrete doesn't pour on a convenient schedule. A slab that has to beat the heat goes in at dawn; a job that lost a day to rain gets made up on Saturday. That means long days and weekend hours land in the timesheet whether you planned for them or not, and the overtime has to be right without you sitting down with a calculator every Friday.
Set each worker's daily and weekly rules once and the math runs itself every week. Break time and overtime are calculated off the same punches that carried through the dead zone, so weekend pours and twelve-hour days are handled without a manual pass.
Two honest notes belong here. Public and prevailing-wage work often carries daily overtime thresholds and certified-payroll rules that vary by state and by the agency on the contract, so set those to what your job and your state actually require rather than assuming a default. And Clox does the arithmetic on the rules you configure; it doesn't decide the rules for you.
Public works is state and agency specific
Daily overtime, prevailing wage, and certified payroll requirements differ by state and by the agency awarding the contract. Confirm the thresholds your job requires with your state labor office or the agency, then configure them once so every week matches.
05
What the week looks like end to end
- 6:45 a.m., crew on site ahead of the truck. Each worker taps clock-in on the way to the forms and picks the job. No signal in the hole, so the punch saves on the phone with its real time.
- The pour runs. Timers keep counting on each phone. Nobody is chasing bars or a paper sheet while the mud is going off.
- Crew climbs out and heads to the next site. The moment a phone catches signal, the queued punches upload with their original times and the job attached.
- The hours land on your dashboard already sorted by pour, with break and overtime math applied to each worker's rules.
- Friday, the times are clean enough to send. Export to your payroll system and the labor-per-job report is already there for the next bid.
Payroll goes out to the system you already run. Clox exports to Gusto, ADP RUN, ADP Workforce Now, Paychex Flex, and QuickBooks Online as CSV, QuickBooks Desktop as IIF, with optional live QuickBooks Online sync and Zapier. The point is that Friday is a five-minute export instead of a rebuild, because the hard part, capturing the pour without signal, already happened at 6:45.
06
Where this fits, and where it does not
This method is built for a concrete or masonry crew that works foundations, flatwork, block and brick, and public jobs, often in places with no signal. If that's you, the workflow above is the day-to-day reality it's designed around.
Two honesty notes so you know exactly what you're getting. Location comes from the phone, so geofenced clock-in is a strong deterrent against punching in from the wrong place, not a foolproof lock; the offline and geofencing posts are clear about that.
And the tamper-evident record proves your punch data hasn't been altered after it was captured, which is what backs a billing or payroll dispute; it doesn't independently prove the GPS reading itself was truthful.
If the no-signal pour is where your hours go missing, the fix is a tracker that captures the punch on the phone before it ever needs a connection. You can start a free trial and run it on your next pour. It's 14 days, no card required, with a 30-day money-back guarantee, so you can put it eight feet down in a foundation and see for yourself whether the hours come back clean.