Ask any superintendent what they think of their current time clock and you will usually hear some version of the same answer: "It works when people use it." The paper sign-in sheet is missing half the names by 9 a.m. The phone app works great for the foreman and nobody else. The punch clock in the trailer is a 15-minute walk from where the crew actually works. And every Monday, somebody in the office spends the morning reconciling hours that do not match the daily log.
Buying a new construction time clock is supposed to fix that. Too often it just moves the problem to a new screen. This guide walks through what actually matters when you pick a time clock for jobsites, the questions to ask vendors, and the mistakes that make crews quietly go back to paper.
The short answer: the best construction time clock is the one that captures every worker at the gate in a few seconds, verifies the person is who they say they are, keeps working when the signal drops, and sends hours and headcounts to the systems your office already uses (payroll, Procore, CMiC) without anyone retyping them. Features like dashboards and reports only matter once that basic capture is reliable.
Why is construction time tracking harder than office time tracking?
Construction time tracking is harder because workers move between sites, many work for subcontractors, signal is unreliable, and dozens of people arrive at once wearing gloves in bad weather. Most time-tracking software was designed for people who sit at a desk, have a company laptop, and work in one place. Construction breaks almost every one of those assumptions:
- Workers move between sites. A carpenter can be on three projects in a week, and each hour needs to land on the right job for cost coding.
- Many workers are not your employees. On a typical GC project, most of the people on site work for subcontractors. You still need to know who is there, even if you do not run their payroll.
- Connectivity is unreliable. Basements, steel structures, rural sites, and new builds without permanent power all create dead zones.
- Gloves, dust, and weather. A system that needs a fingertip on a small touchscreen will fail in January.
- Shift start is a crowd. Thirty or a hundred people arrive within the same 20 minutes. If each check-in takes a minute, you have a line at the gate and people skip it.
- Language. Crews often include workers who are more comfortable in Spanish or another language than in English.
Keep these constraints in front of you when you watch a vendor demo. A slick dashboard is easy to build. Reliable capture at a muddy gate at 6:45 a.m. is not.
What are the main types of construction time clocks?
There are four common types of construction time clock: paper sign-in sheets, personal phone apps, foreman crew entry, and shared gate kiosks where workers scan a badge, QR code or face. Many companies end up combining two of them, such as a gate kiosk with a phone or foreman fallback.
| Approach | How it works | Strengths | Weak spots |
|---|---|---|---|
| Paper sign-in sheets | Workers write their name and times on a clipboard | No cost, no training | Illegible, easy to fill in for others, retyped by hand, often lost |
| Personal phone app | Each worker clocks in on their own smartphone | No hardware, works across sites | Not everyone has or wants to use their own phone, hard to verify identity, battery and data issues |
| Foreman crew entry | Foreman enters hours for the whole crew | Fast for small crews | Depends on one person's memory, no independent verification |
| Shared gate kiosk | A tablet or kiosk at the site entrance where workers scan a badge, QR code, or face | Fast at shift change, one verified record per person, works for subs too | Needs a mounting spot and power, must handle offline periods |
Federal recordkeeping rules let employers use any timekeeping method they choose, so the decision comes down to what works on your sites. For most general contractors and larger subcontractors, a shared kiosk at the gate is the backbone, with mobile and foreman entry as fallbacks for small crews or remote work areas.
Which 8 features actually matter in a construction time clock?
The eight features that matter are check-in speed, identity verification, offline operation, subcontractor and visitor coverage, project and location accuracy, integration with systems like Procore or CMiC, safety and compliance hooks, and permissions with an audit trail. Each one is explained below, with what to ask in a demo.
1. Check-in speed at the gate
Time the check-in yourself during a demo. From the moment a worker steps up to the moment they walk away, it should take a few seconds. Ask how the system handles a line of 40 people. If check-in is slow, workers will skip it and you will be back to chasing missing punches.
2. Identity verification
A time record is only as good as the confidence that the right person made it. Options include:
- QR code or badge scan - fast and cheap, but a badge can be handed to someone else.
- Access cards or helmet stickers - convenient because they stay with the worker's gear, still transferable.
- Facial recognition - confirms the actual person, but brings biometric privacy obligations, such as Illinois's requirement for written notice and a signed written release before collection (see our guide to facial recognition time clocks and biometric compliance).
- Photo capture on punch - a lighter option that lets a supervisor review who clocked in.
Look for a system that supports more than one method, so you can use stronger verification on sites where it matters and simpler options elsewhere.
3. Offline operation
Ask the vendor directly: "What happens if the kiosk loses internet for six hours?" The right answer is that it keeps accepting check-ins, stores them locally, and syncs automatically when the connection returns, with no duplicate or lost records. Anything else means gaps in your data on exactly the sites that are hardest to manage. We cover this in detail in offline time tracking for jobsites.
4. Subcontractor and visitor coverage
A time clock that only covers your own employees misses most of the people on a GC-run site. Check whether the system can track subcontractor workers by company and trade, and whether visitors (inspectors, delivery drivers, owner reps) can sign in without downloading an app.
5. Project, location, and cost code accuracy
Hours need to land on the right project and, ideally, the right location or area within that project. Ask how a worker's check-in is tied to a job: by the kiosk's assigned project, by QR code at a specific location, or by the worker picking from a list. Picking from a list is the most error-prone.
6. Integration with the systems you already run
If you use Procore or CMiC, this is often the deciding factor. The time clock should push manpower and hours into those systems automatically and pull in projects, vendors, and trades so nobody maintains two lists. Ask how sync failures are handled. A good answer includes visible sync status per record and automatic retries.
7. Safety and compliance hooks
OSHA already requires construction employers to instruct each employee in recognizing and avoiding unsafe conditions. The gate is the natural place to confirm that a worker has completed site safety orientation, has the required training level, or has answered a daily health or fit-for-duty check. If your time clock can enforce these at check-in, you get compliance records as a by-product of normal attendance instead of a separate binder.
8. Permissions and audit trail
Someone will eventually edit a time entry. You want to know who changed what and when. Role-based permissions should control who can view, edit, or approve hours, and every change should be logged. This matters for payroll disputes, certified payroll questions on public work, and owner audits. For non-exempt employees, the FLSA also requires employers to keep records of hours worked each day and each workweek, so you want those records to be trustworthy.
Questions to ask every vendor
- How long does a single check-in take, start to finish?
- What happens to check-ins when the device is offline? How long can it stay offline?
- Which verification methods do you support (QR, card, face, photo)? Can we mix them by project?
- How do subcontractor workers and visitors get into the system? Do they need an app?
- Do you integrate with Procore or CMiC? Which data goes each way, and how often?
- How are failed syncs detected and retried? Can I see sync status per record?
- Can the worker-facing screens run in Spanish and other languages?
- Can we require safety orientation or other checks before a worker is checked in?
- What roles and permissions are available? Is there a full audit trail of edits?
- If you offer facial recognition, how do you support biometric consent, retention, and deletion?
- What hardware do we need, and what does it cost to replace a kiosk?
- How long does a typical rollout take for a project our size?
What are the common mistakes when rolling out a new time clock?
Rollout mistakes usually fall into five groups: choosing a system for the office instead of the gate, skipping the conversation with foremen, putting the kiosk in the wrong place, exempting subcontractors, and importing messy master data. Each one is avoidable with a short pilot and a little preparation.
Choosing for the office instead of the gate
The people signing the purchase order usually see the admin dashboard. The people who decide whether the system works are the workers at 6:45 a.m. Run a pilot on one real project before rolling out company-wide.
Skipping the foreman conversation
Foremen and superintendents need to understand what changes for them: less paperwork, fewer Monday calls about missing hours. If they see the new clock as extra work, adoption stalls.
Putting the kiosk in the wrong place
The kiosk should be on the path workers already walk, at the gate or the main entrance, with some protection from rain and direct sun. A kiosk inside the trailer will be ignored.
Ignoring subcontractors
If subs are exempt, your headcounts will not match reality and your Procore manpower log will still be built from phone calls. Make check-in a condition of site access for everyone, and explain it in the pre-construction meeting.
Not cleaning up the master data first
Duplicate vendors, outdated trade lists, and inactive projects all flow into a new system. If your time clock syncs with Procore, do a quick cleanup of the company directory before go-live.
A simple 30-day rollout plan
| Week | What to do |
|---|---|
| Week 1 | Connect integrations, import projects and vendors, set up roles and permissions, configure safety orientation requirements. |
| Week 2 | Install a kiosk on one pilot project. Enroll workers at the gate during the morning toolbox talk. Print and post QR codes for visitors. |
| Week 3 | Compare kiosk headcounts with the foreman's daily report. Fix gaps (missing subs, late arrivals using the wrong entrance). Turn on automated manpower export. |
| Week 4 | Review the pilot with the superintendent and payroll. Adjust settings, then schedule the next projects. |
How do you estimate the payoff?
Estimate the payoff with your own numbers: measure how much unworked time ends up on timesheets and how many office hours go into retyping and reconciling, then multiply by your loaded labor cost. Do not trust anyone's generic "you will save X%" claim, including ours. For example, take one project with 60 workers on site. If inaccurate or padded timesheets add an average of 10 minutes per worker per day, that is 600 minutes, or 10 hours, per day. At a loaded labor cost of $55 per hour, that is $550 per day, or roughly $2,750 per five-day week, on a single project. Your real numbers may be higher or lower; the point is to measure them before and after.
Add the office time too: hours spent each week retyping sign-in sheets, building manpower logs, and answering "who was on site on the 14th?" questions. Those hours are usually easier to measure than time theft, and they disappear quickly once capture is automated. Our guide to buddy punching on construction sites goes deeper on the cost of inaccurate punches.
How ADRO handles this
ADRO was built for the gate, not the office. Here is how it lines up with the checklist above:
- Several check-in methods: workers check in with the gate QR code on their own phone (confirmed by a 4-digit code sent by text), or with an access card or face scan at the kiosk, which can open a turnstile.
- Offline kiosks: ADRO's Raspberry Pi kiosks keep accepting check-ins when the connection drops and sync automatically when it comes back.
- Visitors without an app: visitors scan a QR code at the gate and sign in from their own phone's browser.
- Safety at the gate: safety orientation and training cards are completed at onboarding, workers answer a fine / sick / injured health check at check-in and check-out (with optional blocking), and a presence registry with automated attendance alerts tells you who is expected and who has not shown up.
- Procore and CMiC sync: projects, locations, contractors, and trades import from Procore twice a day, and manpower logs, construction reports, notes, daily uploads, photos, and visitor logs export back, with per-record sync status and an hourly retry for failed manpower logs, reports, notes and uploads. For CMiC, projects, contractors and contacts import, and manpower logs and daily uploads export.
- Control and accountability: custom roles with 80+ permissions, sign-in with a one-time code sent by text, and a record of changes.
- Built for real crews: worker enrollment from a link in English or Spanish or at the enrollment kiosk, and a weekly summary email for the office.
You can see the full feature overview on the ADRO construction time tracking page.
Sources
- U.S. Department of Labor: Fact Sheet #21, Recordkeeping Requirements under the FLSA
- OSHA: 29 CFR 1926.21, Safety training and education
- U.S. Department of Labor: Form WH-347, Davis-Bacon weekly certified payroll
- Illinois Compiled Statutes: 740 ILCS 14/15, Biometric Information Privacy Act (via Onecle)
Want to see it on your own jobsite? Book a 20-minute ADRO demo and we'll walk through it with your projects.