There is a good chance you paid overtime wrong last week. Possibly too much, possibly too little. Either way, it almost certainly was not your team’s fault.

It comes down to how overtime gets calculated when a worker sits on two different shifts at two different rates in the same week. Most agencies handle it the same way, and that way produces a number that is either slightly too high or slightly too low depending on when in the week the worker crossed hour 40.

Slightly too high costs you margin. Slightly too low is a compliance problem.

Here is the whole thing, worked out.

Start with what a shift differential actually is

A shift differential is extra pay for working a less desirable shift. Nights, weekends, overnight, holiday coverage. It sits on top of the base rate for the role.

A picker earns $20 an hour on days and $22 an hour on nights. That $2 gap is the differential. Simple enough on paper.

It stops being simple the moment one worker is on more than one shift, at more than one rate, in the same week. In light industrial staffing, that is not an edge case. It is Tuesday.

Warehouses, manufacturing plants, distribution centres and 3PLs run days, nights and weekends, usually with a premium attached to each. A single worker gets placed on two different shifts, sometimes across two different clients, sometimes spanning two pay periods, inside the same seven days. Multiply that across a few hundred workers on assignment and you have a back office spending its week sorting hours into buckets by hand.

That sorting is the part everyone sees. The overtime calculation sitting on top of it is the part that quietly costs money.

The overtime trap

Once a worker crosses 40 hours in a week and those hours sat at more than one rate, you have to decide what rate the overtime gets paid at.

Most agencies answer that question the intuitive way: pay it at whatever rate the worker happened to be on when they crossed hour 40. If they were on nights, overtime gets calculated at the night rate. If they were on days, it gets the day rate.

That method feels reasonable. It is also wrong, and the direction it is wrong in depends entirely on how the week happened to fall.

If overtime lands on the premium shift, you overpay. Perfectly legal. It just comes straight off your margin.

If overtime lands on the base shift, you underpay. In the US, that is not FLSA compliant.

Same worker. Same hours. Same rates. Two different outcomes, decided by scheduling luck.

What the FLSA actually requires

Under the Fair Labor Standards Act, when a worker earns more than one rate in a workweek, overtime is calculated on the blended average of all the rates they earned that week. Not the rate they were on at hour 41.

You take all straight-time earnings for the week, divide by all hours worked, and that gives you the regular rate. The overtime premium is calculated from there.

The method produces one figure. It does not move based on shift sequencing.

The math, worked out

Take a worker who logs 48 hours in a week. Thirty of those hours are on days at $20 an hour. Eighteen are on nights at $22 an hour. That puts them 8 hours into overtime.

Three ways to calculate the same paycheque.

Method one: overtime lands on nights ($22)

Regular 40 hours: (30 × $20) + (10 × $22) = $820 Overtime: 8 × 1.5 × $22 = $264 Total: $1,084.00

Method two: overtime lands on days ($20)

Regular 40 hours: (18 × $22) + (22 × $20) = $836 Overtime: 8 × 1.5 × $20 = $240 Total: $1,076.00

Method three: FLSA blended rate

Straight time on all 48 hours: (30 × $20) + (18 × $22) = $996 Blended regular rate: $996 ÷ 48 = $20.75/hr Overtime premium: 0.5 × $20.75 × 8 = $83 Total: $1,079.00

The correct figure is $1,079.00.

Method one overpays by $5. Method two underpays by $3. Neither of those is a rounding error your team introduced. Both are the arithmetic working exactly as designed, on a design that does not match the law.

And notice what the blended rate does: it produces $1,079.00 whether the worker’s overtime hours happened to fall on days, on nights, or split across both. The number does not care how the week was scheduled. That is the entire point of the method.

Five dollars, and why it is not five dollars

A $5 overpayment on one worker in one week is nothing. Nobody is losing sleep over five dollars.

The problem is that this is not one worker in one week. It is every worker who picked up mixed-rate hours, every week, across every client site you staff. It is systematic, and systematic is what turns small numbers into real ones.

Run an illustrative model. Take an agency with 300 workers on assignment, where roughly 40 percent of them land in multi-rate weeks. That is 120 affected workers. Assume an average weekly overpayment of about $4 each.

That is roughly $25,000 a year walking out the door in overpayments alone.

Now add the labour. If each affected worker takes about 10 minutes of back-office time per week in preparation, checking and corrections, at a loaded payroll cost of around $35 an hour, you are looking at roughly 1,000 hours a year and about $36,000 in paid time.

Combined, about $61,000 annually, on an illustrative 300-worker model. Your numbers will differ. Plug in your own headcount, your own multi-rate percentage, your own loaded cost. The structure of the calculation holds regardless of what you put into it.

Two things worth sitting with about those figures.

The $25,000 is gross margin. In a take-rate business, that is the most expensive dollar you have. Replacing one dollar of leaked margin takes several dollars of new billings, which means new orders, new fills, new client acquisition. It is a genuinely bad trade.

The $36,000 is paid time, but it is also capacity. Those thousand hours are hours your back office did not spend on redeployment outreach, onboarding, or client service. The work that actually grows an agency.

The third cost, which is not on the P&L

When overtime lands on the base shift and you underpay, that is not a margin question. That is an exposure question.

Underpayment under the FLSA carries back-pay liability across the lookback period, potential liquidated damages, and legal cost. And because the underlying cause is a calculation method rather than a one-off mistake, the exposure is not a single worker in a single week. A claim or an audit scales across every affected worker and every affected week.

That does not show up anywhere on your financials. It sits as risk until it does not.

Canadian agencies are not off the hook here either. Overtime rules vary by province, and the mechanics of the calculation differ from the FLSA. But the underlying problem is identical: one worker, multiple rates, one week, and a calculation that has to allocate hours correctly before it can produce a defensible number.

Why “be more careful” does not fix this

The instinct, when a payroll error surfaces, is to add a check. Another review step. A second set of eyes on Thursday.

That works for mistakes. It does not work for methods.

If your process pays overtime at whichever rate the worker was on at hour 40, then a careful person following that process correctly still produces the wrong number. Reviewing it more closely just confirms the wrong number faster. The error is upstream of anyone’s attention to detail, which is why it survives every process improvement your team has tried.

It is also why the problem gets worse as you grow rather than better. More workers means more mixed-rate weeks. More client sites means more differentials to track. More volume means more hours of manual allocation before you even reach the overtime question. The leak scales with you, and it consumes exactly the back-office capacity you need in order to scale.

How Jombone handles it

This is the part of the process we built to disappear.

Jombone’s shift differential engine recognises every shift and differential attached to a worker, including when those shifts span separate pay periods or sit with different clients. Hours are allocated to the correct shift and rate automatically, with no weekly setup and no re-sorting of timesheets.

When a worker crosses 40 hours, blended-rate overtime is applied automatically. One correct figure, produced the same way every week, regardless of how the shifts happened to fall. For Canadian agencies, the correct provincial overtime rules are applied as part of a one-time setup.

What that removes is the re-work loop. No cascading corrections, no re-running payroll, no off-cycle payments, no compliance guesswork on Friday afternoon.

Setup happens once. After that, the math is just right.

Agencies running automated time capture and pre-payroll validation on the platform operate at over 97 percent timesheet accuracy and under 2 percent payroll exceptions. Shift differentials are one of the specific reasons those numbers hold at volume.

What to check this week

You do not need a platform to find out whether this is costing you. You need about twenty minutes.

Pull last week’s payroll. Find the workers who logged hours at more than one rate and crossed 40 hours. For each one, calculate the blended rate: total straight-time earnings divided by total hours. Compare the overtime you actually paid against 1.5 times that blended figure.

Then count how many workers that applies to in a typical week, and multiply.

Most agency owners have never run that comparison. The ones who do tend to find the same thing: it is not a big number per worker, and it is a much bigger number than they expected in total.

See it handled automatically.

Book a 30 minute walkthrough and bring your most complicated multi-rate week. We will show you what it looks like when the platform does the math.

→ Get a Demo

Ask a staffing agency owner what their markup is and you will get a fast, confident answer. Forty-five percent. Fifty. Fifty-five on the harder class codes.

Ask what their net margin is and the room gets quieter.

Published benchmarks put light industrial markups in the 40–55% range — higher than IT or engineering, largely because of workers’ compensation costs in physical production environments (HumanCloud 2026 benchmarks). Agency net profit margins in the same analysis land at 3–8%.

So you bill 45 points and keep somewhere around 5. Roughly forty points evaporate between the invoice and the bottom line.

Most owners know this abstractly. Very few have mapped where each point goes — and that map is the difference between an agency that can defend its margin and one that just hopes volume covers it.

The Costs You Cannot Negotiate

Start with the floor. A meaningful share of your markup is gone before you make a single operational decision.

Mandatory employer taxes. FICA at 7.65%, plus combined federal and state unemployment insurance that typically lands between 2.6% and 5.6%. That is roughly 10–13% of markup consumed by statute, applying to every placement regardless of role type or how well you run your business (Advent Talent Group / Lone Oak Payroll analysis).

Workers’ compensation. This is the most variable component and the one that hits light industrial hardest. Low-risk office roles may carry rates below 1%. High-risk manufacturing and industrial class codes can run 10% or more.

And it is getting worse. Agencies reaching renewal in 2025 and 2026 are reporting rate increases of 10–25% or more on warehouse, light industrial, logistics, and manufacturing class codes, alongside higher minimum premiums and carriers declining terms on accounts with elevated loss ratios (Risk Placement Services 2026 U.S. Workers’ Compensation Market Outlook, as reported by Akker LLC). Staffing firms are the employer of record on every placed worker, which makes them the responsible party on every claim regardless of whose floor the injury happened on.

Between statutory taxes and workers’ comp on industrial codes, you can be 20+ points into your 45 before you have paid for a single desk, coordinator, or job board post.

That leaves roughly 25 points to cover your entire operation — and produce the 3–8% you keep.

The Leak Map: Five Places Your Margin Disappears

The 25 points you actually control is where agencies win or lose. Here is where it leaks.

Leak 1 — Payroll exceptions.

Every exception costs 30–60 minutes of back-office time to investigate, correct, and resubmit. At industry-average exception rates of 10–15% — often double that on manual workflows — you are funding a meaningful share of a full-time role to do nothing but rework.

The direct labor cost is only half of it. Exceptions also produce off-cycle payroll runs, invoice disputes with clients, and the credit memos that follow. Each of those is margin you already booked as revenue and then gave back.

Leak 2 — The coordinator-per-placement ratio.

This is the leak that determines whether your agency can scale at all.

If every additional 50 placements per week requires another coordinator, your margin is structurally capped. Growth does not improve it — growth just adds proportional cost. You are not building a business with operating leverage; you are building a bigger version of the same business.

The agencies that break out are the ones where volume grows and coordinator headcount does not. That is not a hiring decision. It is an architecture decision, made upstream, about whether the work is manual or automated.

Leak 3 — Vendor stack sprawl.

Every tool in your stack that does not natively talk to the others has two costs: the licensing line item you see, and the integration maintenance you do not. For mid-market agencies, integration upkeep — whether it is a developer, an IT contractor, or a coordinator manually moving CSVs every pay period — commonly runs $10K–$25K annually and never appears on a technology budget.

Then there is what the vendors themselves cost. A separate time clock vendor on per-worker pricing at real volume is a five-figure annual line. Most agencies have not re-examined it since they signed.

Leak 4 — Unfilled and mis-filled orders.

Every order you cannot fill in the window is revenue you never billed. Every no-show is a shift the client noticed, and clients who notice start splitting orders.

The speed bar has moved. An Everee-sponsored 2025 study found that 61% of manufacturing, logistics, and construction companies expect roles filled within 48 hours, and 13% expect same-day. If your fill process runs on call lists and spreadsheets, you are not slow by your own standard — you are slow by your client’s, which is the only one that gets billed.

Leak 5 — Invoice and collections lag.

Margin you have earned but not collected is margin under threat. Every day between the shift worked and the invoice sent is a day of financing your client’s operation with your own cash. Every timesheet dispute at the approval stage delays billing and invites a line-item challenge.

Agencies with manual timesheet approval routinely bill days late and then spend more days defending what they billed. The margin does not vanish — it just costs you working capital and back-office hours to eventually receive.

A Real Example: Ridgepoint Staffing

Ridgepoint Staffing runs 500–600 weekly industrial workers in Orem, Utah. Before consolidating, the leaks were visible on three of the five lines above simultaneously.

Payroll exceptions above 25%. A back office of four people absorbing manual timesheet collection and exception rework. Roughly $42,000 per year going to a third-party time clock vendor, on top of the rest of the stack.

After consolidating onto a single operations platform, exceptions dropped to under 2%. The back office went from 4 FTE to 2. The time clock line went to zero, because the iPad-based biometric clock came with the platform.

“It’s all in one. Multiple platforms in a single one.” — Carlos Figueroa, Head of Operations, Ridgepoint Staffing

None of that changed Ridgepoint’s markup by a single point. Their bill rates are what the market allows. What changed is how much of the markup survived the trip to the bottom line.

That is the part of the equation you control.

What to Measure

You cannot manage a leak you have not sized. Four numbers, tracked monthly:

Exception rate. Percentage of paychecks requiring rework. Above 5% is a project. Above 10% is your project.

Placements per coordinator. Your operating leverage number. If it is flat as volume grows, your margin is capped by design.

Fully loaded tech cost per placement. Every vendor line, plus integration maintenance, plus the coordinator hours spent moving data between systems. Divide by weekly placements. Most operators have never calculated this and most are surprised by it.

Days from shift worked to invoice sent. Your billing velocity. Every day is working capital.

The markup is set by your market. The 40 points between markup and net are set by your operation.

One of those you can do something about this quarter.

See where your agency stands

Take the assessment and find out where your operation sits on the digital maturity pyramid.

Every agency owner knows what it costs to fill an order. Job board spend. Recruiter hours. Screening. Onboarding. Compliance paperwork. Background check. The whole chain runs before the worker sets foot on the floor.

Almost nobody has calculated what it costs to fill that same order with someone who already worked for them last month.

The answer is: a fraction. Sometimes close to nothing.

Redeployment — the share of your temporary workers who finish an assignment and accept another one from you — is the cheapest pipeline your agency will ever have access to. It requires no sourcing spend, no new screening, no fresh compliance cycle. The worker is already in your system, already verified, already known to be reliable or not.

And it is the single most under-managed number in light industrial staffing.

Redeployment Is Not a Recruiting Metric

Here is why most agencies never fix it: they file redeployment under recruiting, and recruiting isn’t where it breaks.

Your recruiters are not the reason a worker doesn’t come back. By the time an assignment ends, the recruiter’s job has been done for weeks. Whether that worker takes your next call is determined almost entirely by what happened during the assignment — and that is operations.

Did they get paid correctly, on time, every week? Did they know their schedule more than 24 hours out? Did their shift change without anyone telling them? Did they have to call the office three times to get a timesheet corrected? Did anyone contact them before the assignment ended, or did it just stop?

Every one of those is an operations question. None of them is a recruiting question. Which means if your redeployment rate is low, hiring more recruiters will not move it.

Industry data underscores how narrow the window is. Analysis of the light industrial market indicates roughly a third of new hires leave within their first 30 days (IMS People, 2026). That is not a sourcing failure — those workers were successfully sourced. It is an experience failure, and it happens on the operations side of the house.

The Math of a Redeployment

Run the comparison honestly.

A net-new fill costs you job board spend, recruiter hours across sourcing and screening, a background check, drug screen where applicable, I-9 and onboarding document processing, orientation, and the risk premium of an unknown worker. Then add the probability that they no-show on day one, and the cost of the backfill scramble that follows.

A redeployment costs you a text message.

Even if you assign generous internal cost to the coordinator time involved, the gap is not close. And the second-order effects compound in your favour:

Redeployed workers no-show less. They have already demonstrated they show up. A first-time placement is a bet; a redeployment is a track record.

Redeployed workers ramp faster. They know your client sites, your supervisors, your process. Client productivity on day one is materially higher.

Redeployed workers are a reliability signal. A high redeployment rate does not just save money — it tells you your talent pool is an actual asset rather than a list of names you rented once.

Clients notice this too. When you send back the same forklift operator who ran their line well last quarter, that is not a staffing transaction. That is a relationship, and it is very hard for a competitor to undercut.

Why Workers Don’t Come Back

Four operational failures account for most redeployment loss. All four are fixable.

1. Pay accuracy.

This is the big one, and it is not close. A worker whose paycheck was wrong — even once, even by a small amount, even if you fixed it the following week — has learned something about your agency that no recruiter pitch will unlearn. Industry average payroll exception rates run 10–15%, and for agencies on manual workflows, often double that. If one in four of your paychecks needs rework, you are systematically teaching a quarter of your workforce not to trust you.

Nobody quits over a $40 correction. They just don’t answer the phone next time.

2. Schedule visibility.

Light industrial workers are frequently piecing together income across multiple sources. When your agency cannot tell someone their shift more than a day in advance, you are asking them to hold time open on faith. Faced with a gig platform that confirms tomorrow’s work tonight, they will take the certainty. Not because they prefer it — because you made them choose.

3. Communication friction.

Every time a worker has to call the branch to resolve something — a missing punch, a rate question, a schedule change — you have spent their goodwill. That call is free to you and expensive to them. Multiply it across an assignment and the accumulated friction is the reason they take the other agency’s call.

4. The silent assignment end.

The most common redeployment failure is the simplest: nobody reached out. The assignment ended, the worker went home, and no one contacted them until the next time you were desperate. By then they had found something else, and your outreach read as transactional — because it was.

The Fixes

Make redeployment a tracked number, weekly. Most agencies cannot state their redeployment rate. If you cannot measure it, you are not managing it. Start by counting: of the workers who ended assignments last month, how many took another placement from you within 30 days? That number is your baseline.

Fix pay accuracy before anything else. Every other redeployment intervention is downstream of this. If your exception rate is in double digits, no amount of engagement programming will fix your redeployment. Pay accuracy is the foundation of worker trust, and worker trust is redeployment. Agencies running automated time capture with pre-payroll validation operate at 97%+ timesheet accuracy and under 2% payroll exceptions — the threshold where pay stops being a reason workers leave.

Trigger outreach on assignment end automatically. Not when you need coverage. When their assignment ends. The system should flag every worker rolling off an assignment and prompt contact before they are cold. This is a workflow, not a discipline problem — if it depends on a coordinator remembering, it will not happen during a busy week, which is every week.

Give workers self-service visibility. Schedule, hours, pay, upcoming assignments — in their hand, without a phone call. Every question they can answer themselves is friction you did not create.

Segment your pool by reliability, not just availability. Your redeployment list is not everyone who ever worked for you. It is the workers who showed up, performed, and left clean. Attendance and performance data should be attached to the worker record automatically, so your first call goes to your best worker rather than whoever is at the top of the spreadsheet.

A Real Example: Ridgepoint Staffing

Ridgepoint Staffing in Orem, Utah runs 500–600 weekly industrial workers. At that volume, the difference between a healthy redeployment rate and a poor one is not a rounding error — it is whether your recruiting team spends its week backfilling the same shifts or building pipeline ahead of demand.

Before consolidating operations onto a single platform, Ridgepoint was running payroll exceptions above 25%. Their back office had four people, and most of their week went to manual timesheet collection and exception cleanup — the exact work that produces late and incorrect paychecks.

After consolidation, exceptions dropped to under 2%. The back office went from 4 FTE to 2.

“We had an extra two, three employees, now we don’t.” — Moises Ramirez, CEO, Ridgepoint Staffing

The headcount number is the headline. The quieter result is what happens to a workforce when four out of five paychecks stop being wrong: the reason not to come back disappears.

Where to Start

This week: calculate your baseline. Of workers who ended an assignment in the last 60 days, what percentage took another placement from you? Most agencies are surprised, and not pleasantly.

This month: audit your payroll exception rate by category. If it is above 5%, that is your redeployment project. Everything else is secondary.

This quarter: build the assignment-end trigger. Every worker rolling off gets contacted before they go cold — automatically, not when someone remembers.

Redeployment is not a retention program or a loyalty initiative. It is the accumulated result of whether your operation treats workers like people whose time and money matter. Fix the operation, and redeployment fixes itself.

Is your agency’s operation built to hold onto the workers you already have?

See where your agency stands

Take the assessment and find out where your operation sits on the digital maturity pyramid.