Time Tracking for General Contractors: Multi-Site Crews and Audit-Ready Records
A general contractor is rarely the one swinging the hammer. You're coordinating several crews, sometimes several subs, across several sites that all bill differently, and you're the one who has to prove where the hours went when a client, an auditor, or your own margin report asks. This guide covers the method: how to make every punch land on the right worksite and job as it happens, how to check sub invoices against your own record, how per-site rollups turn Friday into an approval instead of a reconstruction, and how a signed, tamper-evident record holds up when a dispute lands.
JULY 10, 2026 · BY THE CLOX TEAM
A general contractor is rarely the one swinging the hammer. You're the one holding six jobs in your head at once. There's a kitchen remodel that's three days behind and a light commercial build where the framers just wrapped.
There's a tile sub who invoiced for a day you're not sure he worked, and a client on the second job who is already questioning the last draw. Your own crew is spread across those addresses, and so is the labor cost you're supposed to be tracking against each contract.
That's the real job, and it's why time tracking for a GC is a different problem than it is for a single-trade shop. You're not tracking one crew on one site. You're coordinating several crews, sometimes several subs, across several sites that all bill differently, and you're the one who has to prove where the hours went when a client, an auditor, or your own margin report asks.
This guide is about that method: how to make every punch land on the right site and the right job as it happens, and how to keep a record that holds up when someone disputes it later.
What this guide is and is not
This is the day-to-day workflow for running hours across multiple sites and subs, and the specific Clox mechanisms that make it hold. It's not the pitch for whether Clox fits your shop. That lives on the general contractors page linked at the end. It also doesn't re-explain the nuts and bolts of multi-site setup or how geofencing works, because we wrote those up separately and link them where they belong.
01
The 6:45 reality: you cannot be on every site
On a single-trade job, the owner is usually standing on the slab and can see who showed up. As a GC, your morning is a windshield tour. You leave the house, swing past the remodel to unlock and point the crew at the day's work, then drive to the commercial site to meet the inspector.
By the time you have made the loop it's 9:30, and you have personally witnessed maybe forty minutes of the eight hours you're paying for that day.
Everyone else is on the honor system, or on your superintendent's memory, or on a group text that scrolls past the actual start times. That gap is where a GC bleeds money, and it doesn't look like theft. It looks like a framer who rounds up to a clean start time, or a sub who bills a full day for a half day of no-shows.
It looks like a Friday where you rebuild the week from what people say instead of what happened. The fix isn't standing on more sites. It's making the punch itself carry the truth so you don't have to be there.
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.
02
Two tags, and a GC needs both kept straight
The thing that breaks for a general contractor specifically is that where the work happened and what you bill it against aren't the same. A single address can host a demo phase, a rough-in phase, and a punch-list phase that you invoice as separate line items or even separate contracts. A phased build can move down the block across three addresses that all belong to one job.
If your hours only know the address, your reports tell you where people stood but not what it was worth.
- Worksite is the physical address. It's what a client points at when they ask where your crew was, and it's what a geofence can watch.
- Project or job is the thing you bid, bill, and hold margin against. One job can span several worksites, and one address can host several jobs over its life.
Clox tags every punch with both, at clock-in, so the split is captured while it's still true instead of guessed at on Sunday night. The full walkthrough of setting that up, and the honest take on when a spreadsheet is still enough, lives in the multi-site guide. If you run several addresses, read that one first, then come back for the GC-specific parts below.
03
Subs are the part a GC gets wrong
Here's where a general contractor's workflow diverges hardest from a single-trade crew, and where it pays to be honest about what any tool can and can't do. You don't employ your subcontractors. You can't put a sub's independent crew on your time clock and tell them how to run their day without wading into worker-classification territory you don't want to be in.
So the clean version of this is simple: track your employees in Clox, and treat sub hours as what they actually are, an invoice you verify against your own record of the day.
What Clox gives you there's the counter-record. When a sub bills for Tuesday on the Riverside job, you can pull your own crew's punches for that site and that day. You can see whether the work they're billing around actually lines up with a day your people were on-site and progressing.
It doesn't audit the sub's hours for you. It gives you a timestamped, site-tagged version of events that's stronger than memory when the invoice looks generous.
Do not put a sub's crew on your clock to police them
Directing an independent sub's crew on when and how to clock in can blur the line between a subcontractor and an employee, and that's a classification question for your CPA or attorney, not a time-clock setting. Track your own people. Use your record to check the invoice, not to run the sub's day.
04
Per-site rollups are the number you actually run the business on
The reason to capture site and job on every punch isn't tidiness. It's that at the end of the week the arithmetic is already done. Because each punch already carries its worksite and its job, your reports total labor by site and by project without you rebuilding anything. You open one screen and see every active job, who's on each, and total labor hours to date against it.
For a GC that number is the whole game.
- It's the actual labor cost on the job you're about to invoice, which is what a progress draw should be grounded in.
- It's the estimated-versus-actual labor on the job you just closed, which is the only honest input for bidding the next one like it.
- It's the line that tells you a job you thought was profitable is quietly running thin while there's still time to do something about it.
The same week, seen two ways. Only the per-site rollup tells you what to do about it.
None of those reads are available to a GC whose hours live in a text thread. The whole point of tagging at capture is that the report is trustworthy enough to act on before the money is gone, not just accurate enough to explain the loss afterward.
05
The dispute is coming: proof that survives it
Every general contractor eventually meets the same three conversations.
- A client disputes a draw and wants to know why the labor line is what it is.
- A workers' comp auditor asks you to substantiate payroll by class of work.
- A retention holdback turns into a fight where the other side's version of who was on-site and when is conveniently different from yours.
In all three, a report you could have edited last night is worth exactly as much as the person reviewing it decides to trust you, which on a bad day isn't much.
This is the GC-specific reason Clox records are built to be tamper-evident, not just accurate. Every punch is written into a signed, hash-chained ledger. In plain terms, each record is cryptographically linked to the one before it, so a punch can't be quietly changed, backdated, or deleted after the fact without breaking the chain in a way that's detectable.
When a dispute lands, you can export a signed record and hand the other side a public verification page. An auditor or attorney can check for themselves that the record was produced by Clox and hasn't been altered since capture.
What proof-of-presence does and does not prove
Be precise about this, because overstating it is how you lose credibility in the room. The signed ledger proves the integrity of the record after it was captured: that these punches, times, and tags are exactly what Clox recorded and were not edited later. It doesn't prove the GPS reading itself was truthful, because location still comes from the worker's phone. It settles "was this record altered," not "was the phone honest." Those are different questions, and conflating them is exactly the overselling to avoid.
That distinction is the honest frame every GC should carry into a dispute. Geofencing is a deterrent that discourages the off-site punch. Proof-of-presence is the seal that stops anyone, including you, from rewriting the record after the fact.
Together they let you say two true things: the punch had to originate at the site to count, and the record you're showing hasn't been touched since. For how the geofencing half actually works and where its limits are, the pillar covers it in full.
06
Managers who edit shifts, and the record that shows they did
On a GC's jobs, edits are legitimate and constant. A crew forgets to clock out and you fix it. Someone punches the wrong job and you move the hours. The risk isn't that edits happen, it's that they happen invisibly, so the timecard a client sees looks pristine when it was actually reconstructed.
Clox handles that the way it should: when a manager edits an employee's shift, the change clears that employee's certification, and they have to re-certify the corrected timecard. The edit is visible, attributed, and acknowledged rather than silently baked in.
For a general contractor that's the difference between a record that survives scrutiny and one that invites it. You can correct a genuine mistake and still hand over hours that show their own history, which is a far stronger position than a clean-looking sheet with no trail behind it.
07
Friday: one export, in the format your back office already speaks
The week should end as an export, not a reconstruction. Because the hours are already totaled by person, by site, and by job, with overtime and break math applied, closing the week is approving a sheet that's already right and sending it where it needs to go.
Send a CSV into QuickBooks Online, Gusto, ADP RUN or Workforce Now, or Paychex Flex, or an IIF into QuickBooks Desktop. Hand your CPA a clean PDF of every punch with the pay rules already applied when an audit or a certified-payroll filing needs it.
The GC rule of thumb
Tag every punch with its worksite and its job from day one, and never let hours exist untagged. If you can't answer "what did the Oak Street job cost me in labor, and can I prove it" without opening three tools, your hours are being tracked but not attributed, and that gap is exactly where thin margins and lost disputes come from.
08
Put it together
The method for a general contractor isn't complicated once the tags do the work.
- Capture site and job on every punch so attribution is true at the moment it happens.
- Track your own employees and use that record to check sub invoices instead of trying to run the sub's day.
- Read per-site rollups to catch a thin job while there's still time.
- Lean on a signed, hash-chained record so that when the dispute comes, and it will, you're handing over proof of an unaltered record rather than asking to be believed.
If the workflow above is the one you're already fighting on Fridays, the fastest way to see it is to run a real week through it. You can start a free trial in a few minutes. It's 14 days, no card required, and a 30-day money-back guarantee if it doesn't earn its place on your jobs.