A quick honesty note before the story: this is a composite. The contractor below isn't one customer — it's a picture assembled from the electrical contractors we work with, and every outcome cited is either a product fact or an approved range we publish everywhere. No name, because we don't publish a customer's name without a signed release. The payroll headaches, though, are the real ones.
Every Thursday, the office manager built payroll from three different paper sources: handwritten job tickets, a sign-in sheet at the shop, and whatever the crew leads remembered to text her. Every Thursday, something didn't add up.
At a glance
| Industry | Electrical — residential, commercial, and project work (panel upgrades, generator installs, EV charger installs) |
|---|---|
| Team shape | Around 18 electricians across 3 crews, 1 office manager handling payroll |
| Service area | A mid-size metro market with a mix of storm-season surge demand and steady commercial contracts |
| Before | Paper job tickets, a shop sign-in sheet, and text messages from crew leads reconstructed into a weekly payroll spreadsheet |
The challenge: three paper sources, one payroll run, zero confidence
Picture a shop that looks like a lot of the industry. Eighteen electricians split across three crews, running a mix of reactive no-power calls, commercial maintenance contracts, and multi-day panel-upgrade and generator-install projects. One office manager is responsible for turning all of that into a payroll run every week.
The problem wasn't any one broken piece — it was three sources that never agreed. A crew lead's paper job ticket said a generator install ran nine hours. The shop sign-in sheet, filled out whenever someone remembered on the way out, said the crew clocked out at 4:15. A tech's text message from the truck said they were "probably close to eight, maybe more." None of those numbers were dishonest. None of them were reliable, either.
Two things made it worse. First, storm season. When a windstorm knocked out power across half the service area, three crews ran back-to-back emergency calls for four straight days — and by the time the paper caught up, nobody could reconstruct which hours were regular time and which had crossed into overtime. Missing or incorrect time punches are one of the costliest categories of payroll error there is: research from EY found that missing or incorrect time punches alone cost companies an average of $78,700 per 1,000 employees, per year — and fixing a single payroll error costs $291 on average, once the direct correction and the labor to catch it are both counted, according to EY's 2022 payroll-error-cost study. At 18 people, a shop doesn't need many missed punches before that adds up to real money.
Second, job costing. Payroll wasn't the only thing riding on those paper tickets — so was knowing whether the $14,000 generator install actually made money once labor was counted, or whether the crew quietly ran two days over the estimate. Without hours tracked at the job level, the office manager could tell you what the crew got paid. She couldn't tell the owner which projects were actually profitable.
None of this was unique to one shop. Employers are required to keep a record of "hours worked each day" and "total hours worked each workweek" for every non-exempt employee under the Fair Labor Standards Act, per the U.S. Department of Labor's Fact Sheet #21 — a requirement a sign-in sheet technically satisfies and practically doesn't, since nobody can defend a handwritten time months later with any confidence. And the correction burden is common enough to be well documented: business owners report needing to correct roughly 80% of the timesheets their employees submit, according to a QuickBooks Time survey. Three paper sources that don't agree is a fast way to live inside that 80%.
What changed
Deployment took weeks, not a quarter. We'll be honest about the sequence: week one, crew structure and job types were configured and the office manager ran a parallel week — old paper process alongside the new digital timesheets — to compare the numbers before trusting them. Week two, all three crews were clocking in and out from the mobile app instead of the shop sign-in sheet. By the first storm event after go-live, on-call and emergency-call hours were logged the same way as every other shift — no separate system, no separate math.
Three things carried the load:
Time tracking at the source. Clock-in, clock-out, hours logged against the specific job, and break time tracked as its own status — captured live in the field instead of reconstructed from memory or a paper ticket at the end of the week.
Hours tied to the job, not just the day. Every hour a crew logs attaches to the project or service call it belongs to, so work-order budget tracking shows labor against the estimate while the project is still running — not after the invoice, when it's too late to do anything about it.
Automatic mileage tracking (Pro and Enterprise plans). Every drive between jobs is logged automatically as an IRS-ready mileage record — date, distance, and business-versus-personal classification — exportable as a year-end CSV, with no second app for the crews to remember to open.
The outcome
We keep composite claims honest, so here's what we can stand behind:
- Time tracking at the source — labor data captured live in the field instead of reconstructed from memory, replacing the three-source guesswork the office manager used to reconcile every Thursday.
- Automatic, IRS-ready mileage tracking (Pro and Enterprise plans) — no second app for crews to run, no year-end scramble to reconstruct a mileage log.
- Job-level labor visible while the project is still running — the generator-install question ("did we make money on this one?") gets answered in week two of the project, not the week after the invoice went out.
- Weekly emailed reports summarize revenue, jobs, and utilization automatically, so the owner sees the week's numbers without pulling three separate sources together.
The line we hear most, in one form or another, from the electrical contractors we work with after the first storm season on the new system: payroll stopped being a Thursday-afternoon reconciliation project. The numbers just already agreed.
What a shop like this runs today
The same eighteen electricians, the same three crews — with clock-in and clock-out captured at the source, labor tied to the job it belongs to, and mileage logged automatically instead of remembered at tax time. Storm-season overtime shows up in the numbers the same day it happens, not three weeks later when someone's trying to reconstruct a windstorm from memory. If you want the fuller breakdown of what to track on a digital timesheet and why, see the companion guide; if you want to see the feature itself, see how digital timesheets work in FSM Navigator.
If your payroll run depends on reconciling a paper ticket, a sign-in sheet, and a text message every week, you already know one of them is wrong. You just don't know which one, or by how much.