SOW Misclassification: How Much of Your SOW Spend Is Really Staff Aug?

Last updated: September 30, 2026

By Mike Carter, Managing Director, KORE1

SOW misclassification is staff augmentation bought on a statement of work: named people, directed by your managers, billed by the hour against timesheets. No industry dataset tells you how much of your SOW spend it covers. You get that number by auditing your own ledger.

Three numbers are going around procurement teams about how big this is. More than 20 percent. Upwards of 40. Up to half. I traced all three back this month, because a client wanted the first one on a slide for their CFO’s quarterly review, with Staffing Industry Analysts printed underneath as the source.

It isn’t SIA’s number.

None of that makes the problem small. Reagan is Senior Director of SIA’s CWS Council and has been in contingent workforce management since 1990, so when he says up to half, I take it seriously as a direction. As a figure for a board slide? No. Your share could be 6 percent. It could be 60. That spread between companies is the whole point, and the only way to find where you sit is to open the SOWs one at a time.

Fair warning on where I sit. We place contract engineers, analysts, and IT staff on W-2 through our contract staffing practice, so some of what an audit like this surfaces turns into work we’d happily quote. I’ll also tell you where the audit should leave an SOW alone. That list isn’t short.

What Counts as SOW Misclassification

An SOW is misclassified when the contract says outcome and the working relationship says labor. The supplier names the people, your managers choose and direct them, the work bills by time against timesheets, and the supplier carries no real delivery risk. The paperwork is a statement of work. What you bought is staff augmentation.

Reagan’s column puts the genuine version in one sentence. The provider “would determine delivery, manage the associated workers, retain substitution rights for those workers and carry meaningful commercial risk.” Strip out those four and what’s left is somebody’s time at a consulting rate.

This is not the misclassification your employment lawyer loses sleep over. That one is 1099 contractors who should have been on W-2, and the IRS and state labor departments chase it hard. An SOW worker is usually on somebody’s payroll a few tiers down the supply chain, taxes withheld, so no agency comes looking. Which is exactly why it grows. Nobody audits it except you.

If the real question is which model the work should have been bought under before anyone signed, I wrote a separate piece on choosing between augmentation, consulting, and managed services. This one assumes the contracts already exist and somebody has to sort them.

Washington Wrote This Test Decades Ago

Federal agencies sort this problem under a different name. They call it a personal services contract, and FAR 37.104 bars agencies from awarding one without statutory authority, because getting employees through a services contract circumvents civil service hiring law. The regulation reduces the whole thing to a single question: will the government “exercise relatively continuous supervision and control over the contractor personnel performing the contract”?

Then it gives six descriptive elements to check. Here they are, translated out of federal and into the way a private company would recognize them.

• On site. Or on your VPN every weekday, which is the same thing now.
• Your laptop, your Jira board, your Snowflake account. The FAR’s phrase is “principal tools and equipment furnished by the Government.”
• The work sits inside a team you run, not beside it.
• You have employees down the hall doing comparable work. This one usually ends the argument.
• The need will outlast a year. Look at the extensions.
• Somebody on your side has to direct the work day to day, because the supplier can’t or won’t.

No private company is bound by the FAR. It’s still the cleanest checklist I know, written by people who had a statute behind them, an inspector general reading over their shoulder, and no reason whatsoever to go easy on a program office that wanted its favorite contractor to stay.

Running the Audit on Your SOW Ledger

Most companies start in the wrong system. The SOW module in the VMS only holds what came through the program, and misfiled engagements are disproportionately the ones that didn’t. Start in accounts payable. Our contingent workforce management guide calls the spend inventory the first job of any program. For SOWs specifically, it runs in this order.

1. Pull every supplier invoice coded to professional services, consulting, IT services, or outside services for the last 18 months. Pull it from the ERP, whether that’s NetSuite, SAP, Oracle, or Workday Financials, not from the VMS.
2. Flag time-based billing. Hourly or daily rates, invoice lines that read “J. Patel, 160 hrs,” timesheets stapled on as backup. A fixed-fee milestone invoice rarely belongs on this list.
3. Count heads per SOW. One or two named people is the classic pattern, and Telischak lists “contracts with only one or two resources” among the red flags managers should be trained to catch.
4. Count extensions on the same named person. Two or more and you’re looking at a role, not a project.
5. Spend fifteen minutes with the manager. Not the supplier. The manager.
6. Sort every flagged SOW into three piles and put a dollar figure on each pile.

Step five is where you actually learn something. I’d ask five questions and write the answers down verbatim. Who picked this person? If they were out sick for two weeks, who would find the replacement? What’s the deliverable, and when did it last change? Who approves the hours? Would you notice if the supplier’s account manager quit?

“I did. I would. It keeps moving. Me. No.” A manager who answers like that has told you what the contract won’t.

Expect some pushback in the interviews, and don’t read it as bad faith. Most managers who ended up with a staff-aug SOW got there because the contingent program was slow, or capped tenure at 18 months, or had a rate card that couldn’t touch the skill they needed. Telischak makes the same point from the program side. If the sanctioned channel is painful, managers route around it, and every one of those workarounds lands in your services spend with a project name on it. So fixing the SOWs usually means fixing the program too, starting with a written contingent program policy that managers can actually follow.

What One Misfiled Engineer Costs

A fintech in Newport Beach went through this last spring. Their data platform lead had a senior data engineer on a time-and-materials SOW from a four-person consultancy. $210 an hour. Fourteen months in, third extension. The engineer sat in the team’s standups, took tickets off the lead’s board, and held admin rights in the production Snowflake account. The deliverables section of the SOW said “data platform modernization support.” That was the entire scope. Four words.

Here’s the part that stung. He had started at the company as a contractor through its MSP program, hit the program’s 18-month tenure cap, and came back five weeks later on the consultancy’s paper, doing the same job for the same lead at a higher rate. Reagan calls this hidden tenure. Moving someone from contingent labor onto an SOW “does not remove tenure or dependency risk,” he writes; it “simply hides it.” Caps like that are common. In a March 2026 column, Reagan cites SIA’s Workforce Solutions Buyer Survey: 71% of Americas-region organizations impose tenure limits, and plenty of them are company policy rather than anything the law requires.

Our 2026 tech contractor rate guide puts a contract data engineer’s bill rate at $108 to $175 an hour. Take the top of that range, which is the kindest comparison to the SOW.

2,240 hours is fourteen months at roughly 160 billed hours a month. Call it $78,000 to $153,000 for one person. And the money was the smaller problem. When the engagement finally ended, nobody told IT to pull his Snowflake access, because as far as IT’s records went he had never been there at all, and the login was still live five weeks after the consultancy’s last invoice cleared.

Multiply by however many of these your audit finds. That’s the number that belongs on the CFO’s slide, and it’ll have invoices behind it.

Three Piles, and What Happens to Each

Reroute It

The work is staff augmentation, so buy it as staff augmentation. Through your contingent channel, against a rate card, with tenure tracking and an offboarding checklist that IT actually receives. Often the same person keeps the seat, the same manager keeps directing the work, and the only things that change are whose paper it sits on and what it costs by the hour.

Read the consultancy’s master agreement before anyone makes that call to the engineer, though. Most boutique firms write in a non-solicitation clause or a conversion fee, and walking their person over to a new W-2 employer without checking is how a cost-savings project turns into a demand letter. If the incumbent can’t move, a replacement search through a staffing firm is the fallback. Ours averages 17 days to hire on IT roles, and 92% of our placements are still in the seat at twelve months. Other firms publish their own numbers. Ask for them.

Restructure It

Sometimes the work really is a project and the SOW is just written like a labor contract. Rewrite it so the supplier owns something. Deliverables with acceptance criteria, supplier-controlled staffing with a real substitution right, milestone billing or capped time-and-materials. If what you need is a small project team that owns a defined deliverable, scope it that way from the start. The pricing and acceptance terms for a genuine SOW engagement are a separate conversation, and worth having before the rewrite goes back to the supplier.

Telischak’s column argues that T&M SOWs can be legitimate for agile software work and specialized consulting, provided they carry progress reviews, penalties for delay, and a checkpoint to move to deliverable-based terms once scope settles. Mostly right, in my view. My reservation is practical. “It’s agile” is the single most common answer to “what’s the deliverable?” in these manager interviews, and it’s right maybe a third of the time.

Leave It Alone

A managed service desk running under an SLA with a rotating bench of twenty analysts is not staff augmentation, whatever the invoices look like. Neither is a two-person security firm that scopes a penetration test, runs it on its own schedule with its own tools, hands over a report in six weeks, and never once shows up in your standup. Don’t reroute those to make the audit look productive. An audit that reclassifies everything has told you it was looking for one answer.

What Procurement Asks Before the Audit Starts

Is 20% of SOW spend really staff aug, or did someone make that up?

Tax agencies ignore this one. Why should legal care?

Procurement or HR, who should own it?

Can a time-and-materials SOW ever be the right call?

Realistically, how long does a first pass take?

What if the person on the misfiled SOW is excellent?

Start With the Longest-Running SOW

Don’t wait for the full ledger pull. Find the SOW in your AP data with the most extensions against one named person and call its manager this week. Ask the five questions. You’ll know within fifteen minutes whether your company is closer to 6 percent or 60, and you’ll have your first line item.

If the audit turns up roles that belong in a contingent channel and you’d like a second opinion on the rates, talk to one of our contract recruiters. Bring the invoices.