Field time tracking and labor hours for electrical contractors

What field time tracking is, and why hours run the money

Field time tracking is the practice of capturing what each worker did with their hours: which job, which task, when they started, when they stopped, and how the day split across the work. Not just a clock-in and a clock-out for the company. The hours tied to the job and the cost code, so the number can do four jobs at once. It pays the worker. It builds the cost of the job. It bills the customer. And it tells you what the work really took, which is the only honest input to the next bid.

Labor is the biggest cost most electrical shops carry, and it is the worst-tracked number in the business. Material has an invoice. Equipment has a rental ticket. Labor has a memory, and memory is where the money leaks. A worker who can tell you on Friday roughly how the week went cannot tell you that 3.5 hours went to the panel swap on Tuesday and the rest to the service call that ran long. So the hours land in a lump, payroll guesses, the job cost is fiction, and the bid that comes off that fiction loses money the same way the last one did.

The whole point is to make the hour a real, attributed record at the moment it happens, instead of a reconstruction at the end of the week. Everything downstream of payroll depends on it. The work order bills the labor it carries. Job costing compares estimated hours to actual hours by cost code. Get the hour right at the source and those systems have something true to stand on. Get it wrong and they all inherit the same bad number.

Why accurate time matters more than any other number

Four things ride on the hour, and every one of them breaks when the hour is wrong.

Payroll comes first, because people get paid from it. An hour padded, an hour missed, an overtime line miscounted, and you are either overpaying or underpaying, and both have a cost. Overpaying bleeds margin quietly. Underpaying gets you a wage claim and a back-pay bill with penalties on top.

Job cost is second. Labor is usually the largest line on a job, so a labor number that is off by ten percent throws the whole job-cost picture off more than any material error would. You think the rough-in came in at budget when it ran twenty hours over, because the hours never landed on the right cost code.

Billable recovery is third. On time-and-material and service work, an hour that nobody recorded is an hour you worked for free. It is the most direct leak there is: the labor happened, the cost was real, and the line never made it onto the invoice.

Labor-law compliance is fourth, and it is the one that turns a sloppy habit into a legal exposure. Overtime, breaks, prevailing wage, and recordkeeping all run off the hours. If the hours are guesses, your compliance is a guess too. The hour is the biggest cost in the business and the one people treat most casually, and that gap is exactly where the money and the risk live.

Where the hours leak: theft, rounding, and windshield time

Time leakage is the gap between hours paid and hours actually worked on the job, and it almost never shows up as one big theft. It shows up as a few minutes here and a habit there, multiplied by every worker and every week.

Buddy punching is the obvious one: a worker clocks in a coworker who is not there yet, or who left early. A few minutes a day across a crew is real money over a year, and a shared paper sheet or a single shop time clock makes it easy. Rounding is quieter. Round every start down to the half hour and every stop up, do it across a crew, and you have built a standing overpayment into the schedule that nobody decided to make. Padded hours are the Friday version: the timesheet gets filled out from memory, and memory rounds in the worker's favor without any bad intent.

Windshield time is the one specific to field trades and the one most often miscounted. Drive time between sites during the workday is generally compensable, but the question is which job it belongs to and whether it was billable. Charge a customer for an hour of driving that was really two stops on one trip and you have a dispute. Pay for drive time and never attribute it to a job and you have a cost with no home. The leak is not just the minutes. It is the minutes landing in the wrong place, so they pay out but never cost-code and never bill.

What is clocking to the job?

Clocking to the job means a worker's hours are recorded against a specific job and a specific cost code as the day happens, not just as one in-and-out for the company day. A daily clock tells you the person was on the clock for nine hours. Clocking to the job tells you those nine hours were four on the hospital rough-in, three on the service call across town, one on drive time, and one in the shop pulling material. Same nine hours. Completely different information.

The daily in-and-out is enough to run payroll and nothing else. It cannot cost a job, because it does not know which job. It cannot bill time-and-material, because it does not know which customer. It cannot tell you whether the rough-in beat the estimate, because it never split the hours by phase. Every downstream use of the hour needs the attribution, and the attribution has to happen at the point of work, because nobody reconstructs it accurately after the fact.

This is the single highest-value habit in field time tracking, and it is where most shops fall short. The worker who switches jobs twice in a day has to re-clock to the new job each time, or the hours pile onto whatever job was open. That feeds the job-costing system covered in the job-costing guide: estimated hours by cost code against actual hours by cost code is the comparison that prices the next bid, and it only works if the clock knew which cost code it was on.

Mobile and GPS time clocks, and the geofence

A mobile time clock puts the punch on the worker's phone, which is the only timekeeping device that is already on every jobsite. The worker clocks in when they arrive, picks the job, picks the cost code, and the time lands in the office in real time instead of on a sheet in a truck. No shared shop clock to buddy-punch, no paper to lose, no Friday reconstruction.

GPS and geofencing add a location stamp to the punch. A geofence is a virtual boundary around the jobsite. Set it up and the app can prompt a worker to clock in when they arrive inside the fence and remind them to clock out when they leave, and it records where the punch happened. That kills the most common buddy-punch, because you cannot clock in from the couch and show a GPS stamp at the site. It also catches the honest mistake, the forgotten clock-out that would otherwise pay someone until midnight.

This is where a field tool earns its place. FieldOS puts the clock on the same phone the crew already uses for photos and work orders, ties each punch to the job and cost code, and stamps it with location so the hour arrives at the office attributed and verifiable instead of as a number someone repeats on Friday. The location stamp is not about watching people. It is about the hour being defensible, which matters most on the day a customer or a worker disputes it.

Paper reconstructed Friday vs digital real-time

The paper timesheet has one fatal flaw: it gets filled out at the end of the week from memory. The worker sits down Friday afternoon and reconstructs five days of work that already happened. Nobody remembers that Tuesday's service call ran 40 minutes long or that an hour went to a supply-house run on Wednesday. So the sheet gets round numbers, eight hours a day, jobs assigned by best guess, and the result looks tidy and is wrong in a dozen small ways.

Reconstructed time is wrong in a predictable direction. It rounds to the convenient, it loses the short tasks, it assigns hours to whichever job the worker remembers best, and it never captures the messy reality of a day that bounced across three sites. The job cost built on it is fiction dressed as data. Worse, you cannot tell which parts are accurate and which are guessed, so the whole sheet inherits the doubt.

Real-time digital capture fixes it by moving the record to the moment of work. The worker clocks the job change when it happens, the hour lands attributed, and the office sees the week build day by day instead of in one Friday dump. When the punch happens on the phone at the site, tied to the job, by Friday there is nothing to reconstruct. The week is already recorded. The foreman is approving real entries, not refereeing a memory contest.

How is overtime calculated for field crews?

Under the federal Fair Labor Standards Act, non-exempt workers earn overtime at one and one-half times their regular rate for hours worked over 40 in a workweek. The workweek is a fixed, recurring seven-day period the employer sets, and overtime is figured per workweek, not per pay period. The regular rate is not always just the base wage either. Certain bonuses and other pay can have to be folded in before the multiplier, which is a place shops get it wrong.

Federal law does not require daily overtime. Some states do. A handful, including California, apply daily overtime rules, commonly over 8 hours in a day, with some applying double time past a higher daily threshold, and some states have their own break and meal-period rules that carry penalties when missed. Which rules apply depends on the state where the work is performed and the worker's classification, so confirm the current state rules and the FLSA against the jurisdiction rather than assuming the federal floor is the whole story.

Accurate time is what makes any of this calculable. You cannot apply a 40-hour threshold to hours that were rounded and reconstructed, and you cannot defend a daily-overtime calculation without daily start and stop times. The clock has to capture the real start, the real stop, and the real breaks, by day, or the overtime math is built on sand. Hedge the thresholds and the rules to the FLSA and the state. Do not hedge the accuracy of the underlying hours, because that is the part that is entirely in your control.

What is certified payroll?

Certified payroll is the weekly payroll report a contractor files on prevailing-wage work, certifying that each worker was paid the required wage and fringe for the classification of work they performed. On federal and federally assisted construction it runs under the Davis-Bacon and Related Acts, and the standard form is the U.S. Department of Labor's WH-347, filed weekly with a signed statement of compliance. Many states have their own prevailing-wage laws, sometimes called little Davis-Bacon acts, with their own forms and their own wage determinations.

The form is unforgiving about hours and classifications. WH-347 records, for each worker, the work classification, the hours worked each day, the pay rate, the fringe benefit amounts, and gross wages. If a worker performs work in more than one classification in a week, the hours have to be split by classification and shown separately, each at the rate for that classification. You cannot lump a day that was half electrician and half laborer into one line. The hours must be exact, by day and by classification, because the certification is signed under penalty and an audit will compare it against everything else.

This is where vague time tracking becomes a real liability. A worker who clocks one daily in-and-out gives you no way to split the day by classification, and a Friday reconstruction is exactly the kind of record that fails an audit. Clocking to the job and the cost code, with the classification captured as the work happens, is what makes certified payroll producible without a fight. The exact form, the wage determinations, and the retention rules vary by program and jurisdiction, so confirm the current requirements for the specific contract before you file.

Time to the cost code and phase

A job is not one bucket of hours. It is rough-in, trim, gear, service, startup, and the punch list, and the hours have to land on the right one or the job cost tells you nothing useful. Cost codes are the labels that split the work into phases you estimated separately and want to compare separately. Clocking to the cost code, not just the job, is what turns time tracking into job costing.

The payoff is the comparison. You estimated 120 hours for the rough-in and 60 for the trim. If the hours come in attributed, you find out the rough-in ate 145 and the trim came in at 50, and now you know exactly where the estimate missed. Lump all 195 hours onto the job with no phase split and you know only that the job ran over, not where, which means you cannot fix the estimate that caused it.

This is the direct feed into the job-costing guide's estimate-versus-actual comparison. Job costing lives or dies on whether labor lands on the right cost code, because labor is the biggest and most variable line. The cost code has to be easy to pick in the field, ideally a short list scoped to the job the worker is already clocked into, or the crew picks whatever is on top and the data rots. Make the right code the easy code.

The approval step before payroll

Time gets approved before it becomes payroll, and the approval is where errors die instead of becoming paychecks. The foreman or the office reviews the week, catches the missed clock-out that has someone at 14 hours on Tuesday, the job that got no hours when the crew was clearly there, the lunch that never got deducted, and fixes it while the week is fresh and the people are still around to ask.

Without an approval step, the first time anyone looks hard at the hours is after the check has cleared, and now a fix is a correction, a re-run, and an awkward conversation. Approval moves that scrutiny to before the money moves, which is the only cheap place to catch a time error. A foreman who was on the job knows whether the hours look right in a way the payroll clerk never can.

The approval should be fast and specific. The reviewer is looking at exceptions, the entries that do not fit, not re-keying the whole week. A good system flags the outliers, the missing clock-outs and the hours that do not reconcile, so the foreman approves the normal week in a glance and spends the time on the three entries that need a question. Approve the time, then run payroll. Never the other way around.

Time on the work order bills the labor

On service work, the labor on the work order is what you bill, so the hours have to land on the ticket while the truck is still on site. A tech who clocks to the work order captures the billable labor at the moment it happens, and the invoice can go out the same day with the hours already on it. The work-order guide treats the ticket as the single record of the job from call to cash, and the labor line is half of what makes that record worth money.

The leak here is specific and common. The tech does the work, drives to the next call, and the hour that was supposed to land on the first ticket never gets recorded, or gets recorded as a round guess that undercounts the real time. On time-and-material that hour is pure lost revenue. The work happened, it cost you a burdened wage, and it never hit the invoice.

Tying the clock to the work order closes that gap. The tech clocks into the ticket on arrival, the labor accrues against it in real time, and when the job closes the billable hours are already there to invoice, no reconstruction and no missed lines. The same hour that bills the customer also costs the job and pays the worker, captured once, used three ways.

Billable hours vs paid hours, and utilization

Paid hours are every hour you pay a worker for. Billable hours are the subset a customer pays you for. The ratio between them is utilization, and it is one of the most telling numbers in a labor-driven business, because the gap between what you pay out and what you bill out is where margin lives or dies.

Not every paid hour is billable, and that is fine. Drive time, shop time, training, meetings, warranty callbacks, and waiting on a customer are all paid and mostly not billable. The danger is not that the gap exists. It is that you do not measure it, so you never notice the gap widening. A crew that drifts from 75 percent utilization to 60 percent over a year is giving away a quarter of its time, and if the hours are not attributed you will feel it in the bank balance long before you can name the cause.

Measuring utilization requires the attribution that clocking to the job provides. You cannot compute billable-over-paid if the hours never got sorted into billable and non-billable in the first place. Track the non-billable time honestly, by category, and the utilization number becomes a real management lever instead of a guess. A falling number points you straight at the kind of unbilled time that is eating the week.

Tracking non-job time: PTO, shop, and training

Job hours are not the whole payroll, and the non-job hours have to be tracked too or the picture is incomplete. PTO, holiday, sick time, shop time, training, vehicle maintenance, and shop meetings are all paid hours that do not belong to a customer job, and they need their own codes so they land somewhere instead of getting smeared across whatever job was open.

Two things go wrong when non-job time has no home. First, it pollutes job cost. An hour of shop cleanup that gets clocked to the last job the worker was on inflates that job's labor and makes a profitable job look thin for no reason. Second, you lose track of the real overhead. Shop time, training, and PTO are a genuine cost of running the business, and if they hide inside job hours you never see how much labor the overhead is actually consuming.

Give the non-job categories real codes and make them as easy to pick as a job. The goal is that every paid hour lands on exactly one bucket, job or non-job, so the totals reconcile to payroll and nothing gets double-counted or lost. Clean non-job tracking is also what lets utilization mean anything, because you cannot separate billable from non-billable if the non-billable hours are scattered across job codes.

Time to payroll without re-keying

The hour gets captured once and should flow to payroll without anyone typing it again. Every time a number is re-keyed it can be mistyped, and re-keying a whole crew's week from paper into a payroll system is both slow and a reliable source of errors. The approved time should move into payroll as data, not as a transcription job.

Re-keying is where good field data goes to die. A crew can clock to the job all week, the foreman can approve it cleanly, and then a clerk retypes it into payroll on Friday and fat-fingers a 40 into a 14, or drops a job code, and the careful capture upstream is wasted. The fewer hands the number passes through between the punch and the paycheck, the fewer ways it goes wrong.

This is the back half of what a field tool buys you. FieldOS captures the hour against the job and cost code, runs it through the foreman's approval, and hands the approved totals to payroll without a second entry, so the number the worker punched is the number that gets paid and the number that costs the job. One capture, one record, fewer errors, and the hours stay tied to the cost codes all the way through instead of collapsing into a payroll lump the moment they leave the field.

Keeping the time records

Time records are not just for this week's payroll. They are a legal record you are required to keep and the only thing that defends you in a wage dispute or an audit. Under the FLSA, employers have to keep accurate records of hours worked and wages for non-exempt workers, and the recordkeeping rules set retention periods: payroll records are commonly kept for at least three years, and the supporting records that wages are computed from, such as time cards, for at least two years. Prevailing-wage programs and some states require longer, so confirm the rules for the work you do.

When records are missing or sloppy, the law tends to side with the worker. In a wage claim, if the employer cannot produce accurate time records, courts will often accept the employee's reasonable estimate of the hours worked, and you are left disproving a number you have no record to challenge. The absence of a record is not neutral. It works against you.

Keeping the records right is another argument for digital capture. A digital system retains every punch with its job, cost code, and timestamp, so the record exists, is searchable, and survives long after the paper sheet would have been lost in a truck or a filing cabinet. The retention periods and the exact records required vary by the FLSA, the prevailing-wage program, and the state, so verify the current requirements rather than relying on a single rule of thumb. The principle does not vary: keep accurate, contemporaneous records, and keep them long enough.

How GPS and timestamps defend the hours

A time record with a location stamp and a contemporaneous timestamp is hard to argue with, and that is exactly its value on the day the hours are challenged. When a customer disputes a labor line on a time-and-material bill, or a worker claims hours you did not pay, the question becomes whose record is more credible. A punch made on a phone, at the site, at the time, beats a memory or a number written in after the fact.

The defense cuts both ways, which is worth saying to the crew. The same GPS stamp that catches a buddy punch also proves a worker really was on site for the hours they claim. It protects an honest worker from a customer who says the crew left early as much as it protects the company from a padded sheet. The record is neutral. It just tells the truth about when and where the work happened.

This is the practical reason to capture location, and it is worth being plain about with the crew so it does not read as surveillance. The stamp is there to make the hour defensible, not to track people on their lunch. On a disputed bill or a wage claim, the contemporaneous, location-stamped record is the difference between settling on the other side's number and standing on your own.

The metrics that tell you it works

A few numbers tell you whether the time system is doing its job, and all of them depend on hours that are attributed and accurate.

Labor utilization, billable hours over paid hours, is the headline. It tells you what share of the labor you pay for is labor you bill for, and a falling number is an early warning that unbilled time is creeping up before it shows in the bank. Overtime percentage, overtime hours over total hours, tells you whether you are running the crew hot and paying the premium for it, and whether the overtime is on jobs that can carry it or spread across work that cannot.

Job hours versus estimated hours, by cost code, is the one that improves the business over time. It is the direct comparison from the job-costing guide, and it only exists if the hours were clocked to the cost code. Estimated 120 for the rough-in, spent 145, and now the next bid for similar work knows the truth. Track these three and the time system stops being an overhead chore and starts being the feedback loop that prices the work right.

Rolling it out without the crew revolting

The fastest way to kill a time system is to drop it on the crew as a surveillance tool with no explanation. Workers who think the GPS is there to watch them will fight it, find the gaps, and clock in ways that defeat the point. So lead with the why, and be honest about it.

The why is mostly in the worker's favor, and it is worth saying out loud. Accurate time means accurate paychecks, it means the company can prove the hours when a customer disputes a bill, and it means the next bid is priced for the work the crew actually does instead of a number that sets them up to fail. The location stamp protects the honest worker as much as it catches the dishonest one. Frame it as getting the pay right and defending the work, because that is what it does.

Then make the tool easy enough that doing it right is less work than doing it wrong. If clocking to the job takes five taps and finding the cost code takes a scroll through a hundred codes, the crew will lump everything onto one job and you have lost the data. The job should be one tap, the cost code a short list scoped to that job, the clock-in prompted when they reach the site. Easy and explained beats mandatory and resented every time.

How field time tracking breaks down

The failures are not exotic, and they cascade, because one bad hour poisons payroll, job cost, billing, and the next bid all at once. The most common is the daily in-and-out with no job attached, which gives you a payroll number and nothing else. There is no way to cost a job, bill a customer, or compare to an estimate from an hour that does not know where it was spent.

Paper reconstructed on Friday is the next one, and it fails quietly because the sheet looks complete. The numbers are round, the jobs are best guesses, and the short tasks are gone, so the job cost built on it is fiction. No approval step means the first real look at the hours happens after the check clears, when fixing an error is expensive and awkward. Overtime or prevailing wage figured off rounded, reconstructed time fails the moment it gets audited, because the daily detail to defend it was never captured.

Then there is the back-end pair: no payroll integration, so a clerk re-keys the week and introduces errors into data that was clean, and no retained records, so when a dispute or an audit comes there is nothing to stand on. Any one of these turns careful field work into a number you cannot trust. Together they are how a busy shop ends up unable to say what any job actually cost.

What to record on every time entry

Strip the job and cost code off an hour and you are left with a payroll number and nothing that settles a billing dispute or feeds the next bid. Capture the fields that let the same hour pay the worker, cost the job, bill the customer, and defend the record, and capture them at the moment of the punch, not on Friday.

Worker, job, cost code or phase, classification on prevailing-wage work, start and stop times, breaks, and whether the time is billable are the core. Add the location stamp and the device timestamp and the entry holds up on its own in a dispute. The goal is that every paid hour lands on exactly one bucket with enough detail that nobody has to reconstruct or guess what it was.

Common mistakes

• Clocking only a daily in-and-out, so the hours are never tied to the job or cost code.
• Filling out paper timesheets on Friday from memory instead of capturing time as the work happens.
• Running payroll with no approval step to catch the missed clock-out or the wrong job before the check clears.
• Calculating overtime or prevailing wage off rounded, reconstructed time that cannot survive an audit.
• Re-keying the week into payroll by hand, introducing errors into data that was captured cleanly.
• Keeping no retained records, so a wage dispute or audit is decided on the other side's number.
• Letting non-job time, PTO, shop, and training smear across job codes and pollute the job cost.
• Burying the right cost code in a long list, so the crew lumps everything onto one job.

Field checklist

Standards and references

The Fair Labor Standards Act is the federal floor. It sets overtime at one and one-half times the regular rate over 40 hours in a workweek for non-exempt workers, and its recordkeeping rules require accurate records of hours and wages with set retention periods, commonly three years for payroll records and two years for the time records wages are computed from. The FLSA does not require daily overtime; some states do, and some add break and meal-period rules with their own penalties, so confirm the current state rules against the jurisdiction where the work is performed.

On prevailing-wage work, the Davis-Bacon and Related Acts govern federal and federally assisted construction, and certified payroll is filed weekly, commonly on the U.S. Department of Labor's WH-347 form, by classification and hours, with a signed statement of compliance. Many states have their own prevailing-wage laws and their own forms and wage determinations. The forms, the wage rates, and the retention rules vary by program and by jurisdiction and change over time, so verify the current requirements for the specific contract before you file rather than relying on a remembered number.

Your payroll system and your contract documents complete the picture. The contract can require a tighter record than the law does, and the payroll system defines how the approved hours have to arrive. Across all of it the constants are the same: clock the time to the job and the cost code, capture it in real time, and get the overtime and prevailing-wage detail exact, because those are the parts an audit checks and a dispute turns on. Hedge the thresholds, the retention periods, and the forms to the FLSA, the program, and the state. Do not hedge the accuracy of the underlying hours.

Terms and definitions

Field time tracking carries its own vocabulary, and the same idea shows up under different names across a payroll system, a spec, and a labor agreement.

The hour is the unit, but how it is labeled is what makes it useful. Below are the terms that decide whether an hour can pay, cost, bill, and defend itself.

Clock to the job

Recording hours against a specific job and cost code, not a single daily in-and-out for the company

Cost code / phase

The label that splits a job into rough-in, trim, service, and other phases for estimate-vs-actual

Geofence

A virtual boundary around a jobsite that can prompt clock-in and clock-out and stamp where a punch happened

Buddy punching

One worker clocking in or out for another who is not present, a common source of time leakage

Utilization

Billable hours divided by paid hours, the share of labor you pay for that you actually bill

Workweek

A fixed, recurring seven-day period the employer sets, the basis for the FLSA 40-hour overtime threshold

Certified payroll

The weekly prevailing-wage report certifying each worker was paid the required wage and fringe by classification

Regular rate

The pay rate the overtime multiplier applies to, which can include more than the base hourly wage

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is a work order?
• What is job costing?
• Is per diem taxable?
• What is prevailing wage?
• How do you track job expenses in the field?