Reconciling crew overtime to route profitability before you reprice or reassign work
A weekly close for multi-crew field-service companies: fix the FLSA workweek, reconcile time records to paid hours, compute and allocate overtime cost across routes with a documented driver, then compare paid hours to serviced stops and billed revenue before acting on route margin.

Fix the FLSA workweek your payroll actually uses, reconcile time records to paid hours, compute the week's overtime cost at the regular rate, and allocate it across routes with a documented driver. Then compare paid hours to serviced stops and billed revenue for the same week. We recommend treating route margin as provisional until that match is done.
The decision this article settles
When one crew services several routes inside a single FLSA workweek, the overtime premium attaches to the week as a whole, so we recommend allocating it deliberately and treating route margin as provisional until the allocation is done. The steps: fix the workweek boundary, reconcile time records to paid hours, compute the overtime cost, allocate it across routes with a documented driver, then compare paid hours to serviced stops and billed revenue.
The overtime mechanics come from the U.S. Department of Labor's Fact Sheet #23; the allocation method is this article's proposed managerial close, not a rule any source prescribes.
Where the numbers diverge
The divergence starts with the workweek itself. The Department of Labor's Fact Sheet #23, revised October 2019, states that the FLSA applies on a workweek basis, defined as a fixed and regularly recurring period of 168 hours, seven consecutive 24-hour periods, which need not coincide with the calendar week and may begin on any day and at any hour. Different workweeks may be established for different employees or groups of employees. If dispatch reports routes by calendar week and payroll runs a workweek that starts Saturday at noon, your route margin and your labor cost describe two different periods before anyone touches a number.
The second divergence is schedule hours versus paid hours. DOL states that, unless specifically exempted, covered employees must receive overtime pay for hours worked in excess of 40 in a workweek at a rate not less than time and one-half their regular rates of pay, and that an employer who requires or permits overtime work is generally required to pay premium pay for it. Here is the reasoned inference this article builds on: because overtime attaches to hours actually worked in a fixed workweek, and DOL states that averaging of hours over two or more weeks is not permitted, a route margin built from scheduled hours can omit overtime cost whenever actual hours run past the schedule. That is an inference from DOL's rules, not a claim that every schedule understates every route; it is a mismatch to check in your own dispatch and payroll data.
Step one: fix the workweek boundary
Owner: payroll lead, with dispatch confirming the route-reporting period. Pull the workweek definition your payroll provider actually applies, including the start day and hour, for each crew or employee group. Compare it to the period your route and stop reports cover. Evidence that settles this step: a written workweek definition per employee group that matches what payroll computes, and a route report re-cut to the same boundary. If the two periods cannot be aligned in your field-service software, that is a finding, not a formatting problem; note it and carry it into the close.
Step two: reconcile time records to paid hours
Owner: controller or office manager. For the week in question, take the crew's posted hours from time records and tie them to the hours payroll actually paid, including the overtime premium. DOL states that overtime pay earned in a particular workweek normally must be paid on the regular pay day for the pay period in which the wages were earned, so the paid figure is the one that counts. Evidence: time records that sum to paid regular hours and paid overtime hours with no unexplained difference. Any gap between posted hours and paid hours, whether from missed clock-ins or manual adjustments, gets resolved here, before any cost is assigned to a route.
Step three: compute and allocate the overtime cost
Owner: controller. First compute the cost correctly. DOL states that earnings may be determined on a piece-rate, salary, commission or other basis, but overtime pay due must be computed on the average hourly rate derived from those earnings, calculated by dividing total pay for employment, except statutory exclusions, in a workweek by total hours actually worked. DOL also states that the regular rate includes all remuneration except certain excluded payments, and lists expense reimbursements, overtime premiums, discretionary bonuses, gifts, and payments for occasional periods when no work is performed due to vacation, holidays, or illness among the exclusions. Note the qualifier: the exclusion covers occasional non-work periods, not every payment labeled as holiday or vacation pay. If your techs are salaried, DOL says a fixed salary for a regular workweek longer than 40 hours does not discharge FLSA obligations.
Then allocate. This is a proposed method, not a DOL rule: assign the week's overtime cost across the routes the crew serviced using one documented driver, such as hours worked per route or regular-rate wages per route, and keep the worksheet with the payroll record. Pick one driver, write down why, and use it every week so the allocation is comparable over time. The point of the driver is that the overtime premium is a week-level cost under the FLSA; how you spread it is a management choice, and the choice should survive an audit question.
Step four: compare paid hours to serviced stops and billed revenue
Owner: operations leader. For the same workweek, put three ledgers side by side: paid hours by route, serviced stops by route, and billed revenue by route. This is the billed versus serviced distinction. One risk worth checking, as a proposed check rather than a documented fact: if you bill recurring monthly revenue (RMR) on a fixed schedule while crews complete visits on their own cadence, billing and service can drift apart, and a route can look thin because stops were serviced but not yet billed, or look healthy because billing ran ahead of service. Whether that drift exists in your business is exactly what this step tests. Evidence that settles it: a completed-job-to-invoice tie-out for the week, so every serviced stop is either billed or has a reason and an owner. Treat schedule hours as a planning input for next week's board, not as the labor-cost basis for this week's margin.
For context on crew labor cost, Bureau of Labor Statistics Occupational Outlook Handbook data gives national medians, not your cost: median pay for pest control workers was $45,250 per year, $21.75 per hour, and for grounds maintenance workers $40,080 per year, $19.27 per hour, in May 2025. Those are occupational benchmarks. Using them as a route-cost input would require your own wage and hour data, so treat them as a sanity check on rates, not a substitute for payroll.
Keep the audit trail
Owner: controller. The IRS states that you may choose any recordkeeping system suited to your business that clearly shows income and expenses, that the system should include a summary of business transactions ordinarily made in your business books, and that books must show gross income, deductions and credits. The IRS also states that supporting documents include sales slips, paid bills, invoices, receipts, deposit slips and canceled checks, and that all requirements applying to hard copy records also apply to electronic records. For the weekly route close, the proposed trail is: time records, payroll records, the allocation worksheet, invoices and deposit records. The IRS states that employment tax records must be kept for at least four years, and that records must be kept as long as needed to prove income or deductions on a return. If your QuickBooks sync or job costing setup does not let you pull these together for one workweek, that gap is itself a finding.
When the approach changes, and when to bring in help
Three conditions change this recommendation. First, if your crews cross state lines or you operate in multiple states, state and local overtime rules are outside the sources this article draws on and must be checked separately before you automate anything; the DOL fact sheet covers the federal FLSA only. Second, if exempt-status questions arise, the fact sheet's rules apply to covered non-exempt employees, and classification is a legal question this article does not settle. Third, if the reconciliation keeps failing week after week, one possible diagnostic is that the handoffs between field-service software and accounting, not the math, are the problem; treat that as a hypothesis to test against where the errors actually appear, not a settled conclusion. Atom Backends' published prices are the Systems Audit at $5,500 to $9,500 and the Stabilization Sprint at $15,000 to $35,000 and up, per the company's home page; a Modernization Engagement is scoped after diagnosis.
Checks
- Confirm the written FLSA workweek start day and hour for each crew matches what payroll computes.
- Re-cut route and stop reports to the same workweek boundary payroll uses.
- Tie posted time-record hours to paid regular and overtime hours with no unexplained difference.
- Compute the regular rate per DOL: total weekly pay less statutory exclusions, divided by hours actually worked.
- Allocate the week's overtime cost across routes with one documented driver, kept with the payroll record.
- Tie every serviced stop to an invoice or a documented reason it is unbilled.
- Compare paid hours, serviced stops and billed revenue by route for the same workweek before any reprice or reassign decision.
- File time records, payroll records, the allocation worksheet, invoices and deposit records together, and keep employment tax records at least four years.
Questions
Can I average a crew's hours across two weeks to avoid overtime?
No. The Department of Labor's Fact Sheet #23 states that averaging of hours over two or more weeks is not permitted, and that overtime attaches to hours worked in excess of 40 in a single fixed workweek.
Which route should absorb the overtime cost?
No source prescribes an allocation. The proposed method is to allocate the week's overtime cost across all routes the crew serviced using one documented driver, such as hours worked per route, applied consistently and kept with the payroll record.
Do BLS median wages tell me my route labor cost?
No. BLS figures, such as the May 2025 medians of $21.75 per hour for pest control workers and $19.27 for grounds maintenance workers, are national occupational benchmarks. Your route cost comes from your own payroll and hour data.
How long do I keep the worksheets and payroll records?
The IRS states employment tax records must be kept at least four years, and that records generally must be kept as long as needed to prove income or deductions on a tax return.
Sources
- Fact Sheet #23: Overtime Pay Requirements of the FLSA | U.S. Department of Labor
- What kind of records should I keep | Internal Revenue Service
- Recordkeeping | Internal Revenue Service
- Pest Control Workers : Occupational Outlook Handbook : U.S. Bureau of Labor Statistics
- Grounds Maintenance Workers : Occupational Outlook Handbook : U.S. Bureau of Labor Statistics
How we write: AI-assisted drafts from the cited public sources, each checked by three separate automated reviews (technical accuracy, search intent and writing quality) before publication. About Atom Backends.