Time Tracking for Low-Voltage Installers: Projects, Service Calls, and GC Paperwork

Low-voltage sits between the trades. Structured cabling, access control, cameras, AV, fire alarm: the installs run like construction projects, phased over weeks inside a GC's schedule, while the service side runs like a route, two techs bouncing between same-day calls. Most shops run both at once, which means the time system has to keep two kinds of books without becoming two systems.

Here's the method for a low-voltage shop of 3 to 25 techs.

01

What makes low-voltage hours hard

Two revenue shapes, one crew. Project work is bid: profit is estimated hours versus actual, discovered at closeout, or ideally sooner. Service work is billed hourly or per call: profit is captured minutes. When both blur into one timesheet, projects absorb service leakage and neither book teaches you anything.

The GC's site, the GC's clock. On commercial installs you work inside someone else's schedule: badge-in gates, escorts, other trades stepping on your rough-in. Delay time is real paid time, and waiting you control is compensable, so it needs a label, both for payroll and for the change-order conversation when the GC's delays eat your bid.

Phases decide whether you learned anything. Prewire, trim, termination, testing, punch. A project that goes over teaches nothing unless you know which phase did it. Termination overruns are estimating problems; punch-list overruns are quality problems; wait-time overruns are the GC's problem, if you can show them.

Public jobs raise the stakes on classification. Some low-voltage work lands on prevailing-wage projects, where hours per worker per classification per day have to be right at the source. Prevailing-wage overtime and certified-payroll specifics vary by state and by the wage determination on your job, so confirm those rules with your state agency and your CPA. Clox captures and separates the hours; it doesn't set your rates or produce the certified forms, and anyone who tells you their time clock handles the compliance end-to-end is selling.

02

The method

Projects and service get different jobs, same punch. Every install is a job; service runs as a service job per call or per account, matching how you invoice. The tech clocks in once, from the phone, and the tags carry the split: the project at the project, Service call when dispatched mid-day, Travel for the roll. In Clox each hour lands on a job and task at the punch, so the two books separate themselves in real time instead of in Friday's archaeology.

Phases as tasks, one screen only. Prewire, Trim, Terminate, Test, Punch, Travel, Wait. That last one, Wait, is the GC conversation: when the record shows nine tagged hours of standing down for other trades, the extras claim writes itself. Keep the list short, per the cost code rules, and in the crew's words.

Geofence the projects you choose. Off-site punches are blocked for enabled crews: the clock-in for the hospital job happens at the hospital. Location comes from the worker's phone, so it's a strong deterrent rather than proof, captured only at clock-in, never in the background. On badge-controlled sites, the punch and the GC's gate log will simply agree, which is exactly the kind of boring consistency that wins disputes.

A record a GC or auditor can check. Every punch is signed and hash-chained, checkable by anyone on a public verify page, so the hours behind a pay app or a disputed extras claim can be verified independently. For public work, you can export the punch-level records you would pull for a workers' comp or DOL audit, hours separated by job, day, and worker, and hand the file to whoever is asking.

03

What the two clean books buy you

Project side: hours by phase against the estimate, live during the job, so the overrun is caught at trim, not at closeout, and every closeout adds a real data point to the next bid via the labor-data bidding loop. Service side: captured minutes per call, times the burdened rate, against what you billed, which is where unbilled half-hours go to get found. Both feed the same Friday: Clox runs the overtime and break math automatically, approvals happen in one screen, and the export lands in QuickBooks, ADP, Gusto, Paychex, or CSV.

04

Setting it up for a low-voltage shop

1. Jobs: one per install project, service per call or account to match invoicing.
2. Tasks: the phase list above, pruned to what your bids actually price.
3. Worksites and geofences for the projects that warrant them.
4. Punch paths: the phone app for most techs, and the browser at app.getclox.com for the tech who installs nothing.
5. If the day starts with staging at the shop, put a shop kiosk by the door, because that's where the paid day legally begins.
6. Closeout ritual: estimated hours by phase next to actuals, one line each, into the bid file.

Clox is one plan at $29 a month including the first 3 users, then $6 per tech: geofencing, kiosk mode, scheduling, multi-rate pay, offline punches, and the payroll exports all included. Free for 14 days with no credit card, and a 30-day money-back guarantee after that. Start a free trial or see how Clox fits low-voltage work. Run one project and one week of service calls on it, and read the two books you've been missing.