A dispatch board can show when a technician was assigned, but it does not necessarily show every hour the technician worked. A customer may request an emergency visit after the scheduled shift, a supervisor may reroute a crew between buildings, or an employee may finish a repair after the ticket is marked complete. If payroll treats the original schedule as the whole story, the records may miss compensable time and the overtime calculation may be wrong.
The U.S. Department of Labor's Wage and Hour Division explains in Fact Sheet #22 that the Fair Labor Standards Act (FLSA) generally requires covered, nonexempt employees to receive minimum wage for hours worked and overtime at one and one-half times the regular rate for hours over 40 in a workweek, subject to exemptions and other rules. The practical challenge is assembling a complete record from dispatch, travel, field work, and approved corrections.
Treat the workweek as the calculation boundary
Fact Sheet #23 describes overtime as a workweek calculation: the employer uses a fixed, regularly recurring period of seven consecutive 24-hour days, and hours generally cannot be averaged across two or more workweeks. A Monday shift running late cannot be offset by a shorter Friday in the next workweek. Payroll should preserve the defined workweek for each worker and aggregate work across all locations and assignments in that period.
The regular rate is not always just the hourly rate printed on a schedule. Certain additional compensation can affect the rate under the FLSA, so a bonus, differential, or other payment should receive a payroll review rather than being excluded by habit. This article is an operational guide, not a determination that any particular worker is exempt or that every payment is includable; classification and pay calculations should be reviewed under current federal and state rules.
A schedule is a plan, not a time record. Preserve scheduled start and end times because they explain what was expected, then compare them with reported and approved work. The difference is often where the investigation begins: an emergency call, a late customer handoff, an unscheduled repair, or travel that was not on the original ticket.
Record actual time instead of dispatch estimates
The DOL's Fact Sheet #21 says covered employers must keep accurate records for nonexempt employees, including hours worked each day and each workweek, pay basis, rates, earnings, deductions, payment date, and pay period. The FLSA does not require one particular timekeeping format. A mobile punch, approved timecard, or other complete method can work if it records the hours actually worked and can be reconciled to payroll.
Keep event types distinct. A dispatched assignment records authorization; a start or stop punch records an employee's reported time; a supervisor correction records a review; and a client ticket records scope or service outcome. A ticket marked complete at 4:30 p.m. should not automatically truncate a worker's time if the worker remained on a customer call or drove to a second job. Conversely, a schedule extension is not evidence that the employee actually worked every scheduled minute.
Use a correction workflow that retains the original report, the corrected value, the reason, the reviewer, and when the change occurred. Do not overwrite a late punch or require an employee to erase a report just because a manager believes the shift should have ended earlier. StockPoint audit-logs edits and approvals so payroll and operations can distinguish a worker-reported event from a later supervisor decision.
Count travel that is part of the workday
Travel can be a major source of missing field hours. The DOL's FLSA Hours Worked Advisor explains that travel between job sites during the workday is hours worked, including travel between customers and travel from a designated meeting place where employees receive instructions or pick up tools to the worksite. Ordinary home-to-work commuting is generally treated differently, but the facts around a particular route can matter.
Dispatch records should therefore identify the actual sequence of locations and any required work before the first site or after the last one. If a technician picks up equipment at a yard, attends a briefing, or performs job-related work before driving to the customer, preserve those events. Do not infer paid or unpaid status solely from the words "travel" or "commute" in a route description; use the DOL guidance and obtain advice for unusual arrangements.
GPS can corroborate that a device was near a site, but it does not by itself establish whether travel was compensable, who was working, or how long a task took. StockPoint reports GPS with honest accuracy context and ties a verified per-building punch to a shift. Managers still need to review the employee's full sequence of work and travel, including events that occur between checkpoints.
Build a dispatch-change trail
A dispatch change should carry its own timestamp, author, reason, affected worker, customer, and expected response. If an emergency request is accepted by phone, the supervisor can create a follow-up ticket that records when the call came in and what work was authorized. When the field report later differs from the assignment, leave the original instruction intact and attach the revised scope or time note.
The distinction matters for pay as well as billing. A customer may approve a return visit but dispute the time spent diagnosing the problem; payroll still needs the actual hours worked, while the commercial team separately decides what the contract permits it to invoice. Do not let a client charge code determine whether the worker's time is paid. The time record and the customer billing decision answer different questions.
Set clear rules for after-hours calls, texts, and remote troubleshooting. If a technician is asked to read a site log, respond to a customer, or take action, capture the work rather than assuming that a short digital exchange disappears from the time record. The DOL's Fact Sheet #22 discusses work suffered or permitted; a policy against unauthorized overtime is not a substitute for paying for work the employer knows or has reason to know occurred.
Worked example: a callout and a second site
Assume a technician records 39.0 approved hours through Thursday in the employer's established workweek. On Friday the scheduled shift is 8:00 a.m. to 4:00 p.m., but a customer call extends the day and the technician travels from the first site to a second one before returning a company tool. The times in this example are illustrative, not a statement about any employee's actual pay or the precise compensability of every event.
The supervisor should preserve the original schedule, the callout request, the technician's reported start and end events, the inter-site travel, the work performed at the second building, and any required equipment return. Payroll then reviews the complete week and applies the appropriate rules to the actual hours, including overtime if applicable. If the final total is 46.0 hours, that is not made 40.0 by deleting the callback or by averaging it with a shorter week.
Cost-plus billing should be reviewed separately against the contract and the client's approved scope. StockPoint can calculate cost-plus hourly billing from the same approved punches that pay a worker, helping reduce a mismatch between payroll inputs and the invoice. That linkage is useful, but it does not decide whether a travel segment is legally compensable or whether a client will reimburse an emergency visit.
Review meal periods, waiting, and incomplete events
A dispatch gap is not automatically an unpaid meal period. Under the DOL's Fact Sheet #22, a bona fide meal period is generally noncompensable only when the employee is completely relieved of duty; work performed during a meal can be compensable. If a technician must monitor a phone, respond to an urgent call, or remain responsible for a job, the record should capture the facts and prompt a review rather than allowing a blank interval to decide the question.
Create an exception queue for missed stops, overlapping shifts, unexplained travel gaps, long tickets with no corresponding time, and edits made after payroll approval. Ask the employee and supervisor what happened, document the explanation, and correct pay promptly when the review identifies additional time. A GPS stop can support the timeline but cannot prove a duty-free break or negate an employee's account by itself.
The process should also accommodate a worker who has limited mobile access. A phone failure, poor signal, or forgotten PIN should lead to a documented alternate report, not a demand that the employee accept a zero-time record. Photo, PIN, and GPS-based punch verification can help establish a field event, but the employer's correction policy remains essential for exceptions.
Reconcile payroll records to tickets and preserve them
At payroll close, compare reported hours, approved hours, dispatch changes, time outside scheduled windows, and payroll totals. Investigate mismatches before payment where practical, but do not delay undisputed wages while an internal billing dispute is unresolved. Document who reviewed each exception and what evidence informed the decision. A client complaint about service quality is not itself evidence that the worker performed fewer hours.
Fact Sheet #21 distinguishes payroll records from records supporting wage computations and gives retention periods for records within its scope. It describes at least three years for payroll records and two years for time cards and other wage-computation support. Employers should confirm how the federal baseline interacts with state requirements, litigation holds, contracts, and other applicable rules before adopting a retention schedule.
Per-worker payroll locking can prevent the same worker item from being paid twice when a correction is reviewed. StockPoint calculates and prepares 941, NYS-45, and W-2 data, but the employer reviews and files those forms; bank-feed reconciliation is on the roadmap, not shipped. The employer remains responsible for accurate records, tax filings, deposits, and a defensible decision trail.
Use the record system to improve dispatch
A weekly review should look for operational causes, not only individual exceptions. Repeated late calls may signal an unrealistic service window, a customer access problem, or a staffing gap. Frequent travel overruns may point to route design rather than poor timekeeping. Compare scheduled versus actual hours by service type and location, then update bids and staffing assumptions without editing historical punches to make the variance disappear.
Train dispatchers and supervisors on what they may change, what requires employee confirmation, and when payroll must be alerted. Give workers an easy route to report unrecorded work or a disputed correction in English or Spanish. Audit who can approve edits and restrict client portal access to appropriate service evidence rather than private payroll details. StockPoint's operations tools can connect verified building punches, approvals, and client-facing status in one operating record.
If your company needs to connect field dispatch, time review, and payroll preparation without treating a ticket as a timecard, visit getstockpoint.com to sign up for StockPoint. The platform gives field-service teams bilingual workforce surfaces, worker-level payroll controls, and building-level work evidence while leaving the employer in control of review and filing.